Sofaconventions piotr_wiki https://www.sofaconventions.org/mediawiki/index.php/Main_Page MediaWiki 1.39.2 first-letter Media Special Talk User User talk Sofaconventions Sofaconventions talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk 0 1 1 2013-05-14T18:08:02Z MediaWiki default 0 wikitext text/x-wiki '''MediaWiki has been successfully installed.''' Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] b7a3846f2c55072191227d89a3204fe379288fee 2 1 2013-05-17T05:49:22Z Isfmiho 3 Isfmiho moved page [[Main Page]] to [[SOFA (Spatially Oriented Format for Acoustics)]] wikitext text/x-wiki '''MediaWiki has been successfully installed.''' Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] b7a3846f2c55072191227d89a3204fe379288fee 4 2 2013-05-17T05:53:36Z Isfmiho 3 wikitext text/x-wiki * [[What is SOFA]] * [[SOFA Specifications]] * [[SOFA Conventions]] '''MediaWiki has been successfully installed.''' Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] 1f3ea6bf84bc6f9073a709f0bcaf6e6045adc4a5 9 4 2013-05-17T06:11:49Z Isfmiho 3 wikitext text/x-wiki * [[What is SOFA]] * [[SOFA Specifications]] * [[SOFA Conventions]] 44864ec1449918c792dc1db0a70482a0b1010153 22 9 2013-05-17T08:45:29Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[More general information on SOFA]] * [[SOFA Specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA Conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[APIs]] e716e3900e0f365f4d112edae6313e97c508f41c 23 22 2013-05-17T08:45:58Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[More general information on SOFA]] * [[SOFA Specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA Conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] ab30eb7866f49a3148925803c051f4c3f187ac2b 27 23 2013-05-17T09:25:27Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[More general information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA Conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] 8463a2ef8df3d01117683e4f0b9ff3b43ab45846 31 27 2013-05-17T09:27:02Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[More general information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] b4082869328e3779acb8e7d238535b17b352dd94 34 31 2013-05-17T09:28:02Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] f16cee60849ce92476094ae4af1a7d762050ee5d 47 34 2013-05-17T10:03:41Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] f86dc36ec07cf743fada2ec948dd21aee1285a8b 49 47 2013-05-17T10:21:48Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] * [[Data]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] 6e845888922e17906ace9537cd46c48567451811 50 49 2013-05-17T10:22:32Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] * [[Files (HRTFs, BRIRs, DRIRs)]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] 3e55b712626a84a2ac553f0e73e551faa970f476 0 462 3 2013-05-17T05:49:22Z Isfmiho 3 Isfmiho moved page [[Main Page]] to [[SOFA (Spatially Oriented Format for Acoustics)]] wikitext text/x-wiki #REDIRECT [[SOFA (Spatially Oriented Format for Acoustics)]] 6d8cda637970447fc111d87a829792f37610890a 0 3 5 2013-05-17T05:54:06Z Isfmiho 3 Created page with "Head-related transfer functions (HRTFs) describe the spatial filtering of the incoming sound. So far available HRTFs are stored in various formats, making an exchange of HRTFs..." wikitext text/x-wiki Head-related transfer functions (HRTFs) describe the spatial filtering of the incoming sound. So far available HRTFs are stored in various formats, making an exchange of HRTFs difficult because of incompatibilities between the formats. We propose a format for storing HRTFs with a focus on interchangeability and extendability. The spatially oriented format for acoustics (SOFA) aims at representing HRTFs in a general way, thus, allowing to store data such as directional room impulse responses (DRIRs) measured with a microphone-array excited by a loudspeaker array. SOFA specifications consider data compression, network transfer, a link to complex room geometries, and aim at simplifying the development of programming interfaces for Matlab, Octave, and C++. SOFA conventions for a consistent description of measurement setups are provided for future HRTF and DRIR databases. 3666e984dee6c482270c410c07413c2fb547e6ac 0 4 6 2013-05-17T06:02:15Z Isfmiho 3 Created page with "== Objects == Receiver is any acoustic sensor like the ear or a microphone. The number of receivers in not limited in SOFA and defines the size of the data matrix. Listener is..." wikitext text/x-wiki == Objects == Receiver is any acoustic sensor like the ear or a microphone. The number of receivers in not limited in SOFA and defines the size of the data matrix. Listener is the object incorporating all the receivers. For HRTFs, a listener can be a head or dummy-head microphone. For DRIRs, a listener represents the microphone-array structure such as a sphere or a frame. Incorporating the receivers in the listener as a single logical object is important because in measurements, usually the orientation and/or position of the listener vary without substantial changes in the head-microphone relation. For example, in measurements done for multiple positions in a room, the position of the head varies and the relation between the head and the microphones does not change. Note that only one listener is considered. Emitter is any acoustic excitation used for the measurement. The number of emitters is not limited in SOFA. The contribution of the particular emitter is described by the metadata (see later). Source is the object incorporating all emitters. In SOFA, source might be a multi-driver loudspeaker (with the particular drivers as emitters), or a speaker array (with the particular speakers as emitters), or a choir (with the particular human as emitter), etc. Note that only one source is considered but the source may incorporate an unlimited number of emitters. Room is the volume enclosing the measurement setup. In the case of a free-field measurement, the room is not considered. An optional room description is considered for measurements performed in reverberant spaces, with a direct description of a simple shoebox, or with a link to a digital asset exchange file for a more complex description. Optional Objects can be described by including user-defined metadata of a measurement. For example, this might be the information about a torso, as in the measurements in which the angle between the torso and the head is varied as an independent variable. == Relation between the objects == We use two coordinate systems. Source and listener are defined in the coordinate system of the room, called global coordinate system. In free field, the global coordinate system is arbitrary. Emitters and receivers have both their own coordinate system called local coordinate system. The local coordinate system of emitter and receiver are defined relatively to the coordinate system of the source and listener, respectively. With the source and listener in the origin and at default orientation, the local coordinate systems correspond to the global coordinate system. Two vectors describe the basic orientation of the source/listener: the “view” vector defines the direction in which the source/listener looks; the “up” vector defines the top of the source/listener. In spherical coordinates, the view vector describes the azimuth and elevation angles of the source/listener. The up vector describes the roll, which is usually not considered in HRTF measurements and is optional. If given, we suggest the up vector to be orthogonal to the view-vector. The default basic orientation for the source/listener is the view vector on x-axis and the up vector on z-axis. In order to be flexible in the future, the way the position and orientations are defined is specified separately for the listener, source, all emitters, and all receivers. The default coordinate type for the position, view, and up vectors is the Cartesian (x y z). When the spherical coordinate system is required, the format is (azimuth elevation distance). The source/listener basic rotations can be further modified. Most HRTF measurements consider only rotations described by the azimuth and elevation angles. These two angles provide the possibility to describe the rotation of the listener in an intuitive way. However, for arbitrary rotations in the 3-dimensional space the exact order of the rotations becomes important. Rotation descriptions like the "yaw-pitch-roll" system (which is known as DIN 9300 for aviation and more intuitive) or the unit quaternions (which avoid the gimbal lock and are computationally efficient) clearly define the order of rotation. Note that a complete agreement on the coordinates and coordinate systems has not been done yet. == Numeric container == SOFA stores the information in a single file by serializing the data into a binary stream. The serialization is usually done by a numerical container, which defines the format of the binary representation. SOFA files have the extension “.sofa”. In order to avoid custom development of a numerical container, SOFA relies on netCDF-4 (Unidata), which is a set of software libraries and data formats supporting the creation, access, and sharing of scientific data.1 It is self-describing, network-transparent, and machine-independent; it supports huge files, partial access within a file, and allows for data compression. netCDF-4 is widely used in the field of climatology, meteorology, oceanography, and geographic information systems. It is based on the HDF5 (HDF5 Group)2, a more basic numerical container, further supported by many institutions worldwide. For SOFA, netCDF offers a structured representation of multidimensional data and metadata. The open-access specifications are freely available and include a complete definition as well as examples of various implementations. Application-programming interfaces are available as pre-compiled libraries for programming languages like C++, Octave, and JAVA. Note that netCDF is natively supported in Matlab. netCDF considers conventions, a set of recommendations in a community on the naming of attributes, variables, and dimensions within a netCDF file. Many conventions exist, mostly in the field of climate and geographical research.3 SOFA proposes conventions related to the HRTF/DRIR measurement. In particular, SOFA conventions are proposed for typical HRTF/DRIR measurement setups. According to the netCDF terminology, SOFA defines dimensions and stores data in variables and attributes. SOFA uses the so-called enhanced data model from netCDF-4, which is based on the classic netCDF data model shown in Fig. 2. Since the enhanced data model is more complex and not well spread in various computer systems yet, we mostly use the classic data model parts from the enhanced model. This way allows a simple data representation but still full flexibility in the future. More deep knowledge of netCDF format details is not required to read or write netCDF datasets. More interested readers are referred to the User's Manual.4 Note that in SOFA, we sometimes refer to the data type “string”, which is defined in the enhanced data model but is not provided in the classic model. Currently, some computer programs like Matlab and Octave have difficulties handling netCDF strings in a proper way, thus, at the moment, strings as variables are currently not supported. Native support of strings and string arrays is planned after clarification of the technical requirements. == Data == Data represent the numeric description of the acoustic systems and consist of a multidimensional matrix of an arbitrary size. Data stored in this format have the flexibility to be in the domain that best accommodates the measurement and measurement system. Data can be time domain finite IRs (data type FIR) or infinite IR filter coefficients (IIRBiquad), with or without separately stored broadband delays. The broadband delay (i.e., time-of-arrival, TOA) can be stored as discrete delays in a matrix or as parameters of continuous-directional TOA model [26]⁠. Data contain fields (e.g., Data.IR, Data.G) which are functions of the dimension N. The interpretation of N depends on the data type, e.g., for IRs, N represents the sampling interval (i.e., inverse of the sampling rate) or the number of FIR-filter taps. The interpretation is denoted in the attributes of the dimension variable N. The different data types and corresponding fields are shown in Tab. 1. Theoretically, the HRTFs/DRIRs (as a function of discrete spatial position) can be transformed to functions of continuous spatial frequency and represented in the spherical-harmonic (SH) domain. Advantages like the directional continuity or better compactness are the main reasons for such a representation. Even though not provided at the moment, SOFA aims at considering SH data in future conventions (see Sec. 4). == Dimensions == Each netCDF variable has fixed dimensions and its dimensions must be defined before creating the variable. Thus, in SOFA, netCDF dimensions are pre-defined, see 2. Data and metadata are described by using these dimensions. User-defined dimensions are currently not provided. Throughout this document, the matrix sizes are denoted by [A1 A2 … AI] where Ai represents the length of the dimension i of the I-dimensional matrix. For example, assume a database consisting of one thousand measurements, i.e., M = 1000, obtained for 1000 different rotations of the listener, i.e., ListenerRotation is [M C], using two microphones, i.e., two IR per measurement, and sampling rate of 48 kHz. Then, in the netCDF file, M = 1000, R = 2, and C = 3. Further, the netCDF variables “Data.IR”, “ListenerRotation”, and “Data.SamplingRate” have dimensions [M R N], [M C], and [1], respectively. Variables can have different dimensions. For example, it is possible to provide the ListerPosition as a single entry, meaning that the one ListenerPosition is valid for all measurements. But it is also possible to provide a different ListenerPosition for each measurement. Note that there are restrictions on the variant dimensions: The dimensions must be the pre-defined dimensions, see Tab. 2. The size of the dimensions may change, but the number of dimensions must not. In the above example, valid dimensions of the ListenerPositions are [IC] and [MC]. Invalid dimensions would be [C] and [MC]. == Metadata == Metadata consist of variables and their attributes. General metadata (Tab. 3) consider the most important properties of the measurement and are valid for the global measurement setup. In order to keep it simple, nested structures within the metadata are not allowed, but grouping by prefixes, e.g., ListenerPosition and ListenerOrientation is encouraged. Attributes for the geometry description (e.g., source position, listener orientation) extend a value by further coordinate triplet C. When saved as a variable, date and time uses integer number of seconds from 1974-02-22 00:00:00. When saved as attributes string in ISO 8601 format “yyyy-mm-dd HH:MM:SS” is used. === Global attributes === General metadata are represented as global attributes in netCDF. === Object variables and their attributes === Other metadata can be a matrix of numeric (integer or float) variables or a string. Attributes can accompany a variable where appropriate. Object-specific metadata consider the description of objects listener, receivers, source, emitters (Tabs. 4 and 5). Room-specific metadata describe the room used in the measurements and depend on the attribute RoomType (Tab. 2). Measurement metadata describe other measurement-specific data like the time of a particular measurement (MeasurementTime) and have the prefix “Measurement”. === User-defined attributes === Must have explicitly define dimensions using the dimension given in === Room types === == Coordinate systems == === Cartesian === x, y, z as a basis === Geographic (Spherical) === === Din9300 === === Navigational === === Horizontal-Polar === 52374dba1abff61a07ac75edb62681f28764dafc 12 6 2013-05-17T07:45:19Z Isfmiho 3 Blanked the page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 13 12 2013-05-17T07:45:51Z Isfmiho 3 wikitext text/x-wiki available soon... a691d0a86b60477fc7e6c61fe6327194d5e84a40 14 13 2013-05-17T07:47:23Z Isfmiho 3 wikitext text/x-wiki * [[SOFA Specifications v0.1|Specifications v0.1]] * [[SOFA Specifications v0.2|Specifications v0.2]] * [[SOFA Specifications v0.3|Specifications v0.3]] 8deb0ab3bf8ed6962836949a01654593343a8962 0 5 7 2013-05-17T06:08:52Z Isfmiho 3 Created page with "In order to meet the different requirements coming from different application fields, SOFA conventions are specified, i.e., definitions of data and metadata consistently descr..." wikitext text/x-wiki In order to meet the different requirements coming from different application fields, SOFA conventions are specified, i.e., definitions of data and metadata consistently describing particular HRTF/DRIR measurement setups. SOFA conventions can be implemented without any programming by using the Common Data Form Language (CDL) as suggested for netCDF. CDL files allow for a platform-independent interpretation of specifications and can be compiled to a binary netCDF file using the ncgen tool from the netCDF package: ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl The binaries of the nc-tools are available at the Unidata. In the following, two SOFA conventions are described. Note that instead of aiming at foreseeing the future, conventions should be developed only for known measurement setups. The known features should be consistently described while not limiting the development of future conventions. ==Conventions== * [[Stable SOFA Conventions|Stable]] * [[Proposed SOFA Conventions|Proposed]] * [[Discussion & Requests]] 0ca2c62a99d38c1df7a0996f01eba0c04e72815d 15 7 2013-05-17T07:49:59Z Isfmiho 3 wikitext text/x-wiki In order to meet the different requirements coming from different application fields, SOFA conventions are specified, i.e., definitions of data and metadata consistently describing particular HRTF/DRIR measurement setups. SOFA conventions can be implemented without any programming by using the Common Data Form Language (CDL) as suggested for netCDF. CDL files allow for a platform-independent interpretation of specifications and can be compiled to a binary netCDF file using the ncgen tool from the netCDF package: ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl The binaries of the nc-tools are available at the Unidata. In the following, two SOFA conventions are described. Note that instead of aiming at foreseeing the future, conventions should be developed only for known measurement setups. The known features should be consistently described while not limiting the development of future conventions. ==Stable Conventions== * [[SimpleFreeFieldHRIR]] ==Proposed SOFA Conventions== ==Discussion & Requests== 7d262e7ea450e06d617f7dd56c3ed4d511f39e20 29 15 2013-05-17T09:26:45Z Petibub 4 Petibub moved page [[SOFA Conventions]] to [[SOFA conventions]] wikitext text/x-wiki In order to meet the different requirements coming from different application fields, SOFA conventions are specified, i.e., definitions of data and metadata consistently describing particular HRTF/DRIR measurement setups. SOFA conventions can be implemented without any programming by using the Common Data Form Language (CDL) as suggested for netCDF. CDL files allow for a platform-independent interpretation of specifications and can be compiled to a binary netCDF file using the ncgen tool from the netCDF package: ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl The binaries of the nc-tools are available at the Unidata. In the following, two SOFA conventions are described. Note that instead of aiming at foreseeing the future, conventions should be developed only for known measurement setups. The known features should be consistently described while not limiting the development of future conventions. ==Stable Conventions== * [[SimpleFreeFieldHRIR]] ==Proposed SOFA Conventions== ==Discussion & Requests== 7d262e7ea450e06d617f7dd56c3ed4d511f39e20 35 29 2013-05-17T09:42:25Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions ==Stable Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. Measured data exist and the description must be fixed in order to create publicly available SOFA files and software. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a reverberant space * [[SimpleDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source ==Discussion & Requests== Here we discuss suggestions from the peer group * Item 1 (Author 1) * Item 2 (Author 2) 6cb6e8a55c2b35057bc66a5cf7c7822bddef171b 36 35 2013-05-17T09:42:44Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions ==Stable Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. Measured data exist and the description must be fixed in order to create publicly available SOFA files and software. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a reverberant space * [[SimpleDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source ==Discussion & Requests== Here we discuss suggestions from the peer group * Item 1 (Author 1) * Item 2 (Author 2) b6e5df107ef857646a0df74f9122125502db6903 39 36 2013-05-17T09:53:40Z Petibub 4 /* Proposed SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions ==Stable Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. Measured data exist and the description must be fixed in order to create publicly available SOFA files and software. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. ==Discussion & Requests== Here we discuss suggestions from the peer group * Item 1 (Author 1) * Item 2 (Author 2) f4965a36e4172d99c85274ed07d1056f701c5f1e 0 6 8 2013-05-17T06:11:13Z Isfmiho 3 Created page with "==Free-field HRTF measurement of a single listener (SimpleFreeFieldHRIR) == This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other simil..." wikitext text/x-wiki ==Free-field HRTF measurement of a single listener (SimpleFreeFieldHRIR) == This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases (Fig. 2). The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. The corresponding CDL file is provided in the Conventions directory of the SOFA package. ==Microphone-array measurement in a single room (SingleRoomDRIR)== This conventions defines a setup used for measuring DRIRs in a single room with an arbitrary number of receivers (Fig. 4). The setup considers measurements in a room with a single excitation source and a microphone array with an arbitrary number of omnidirectional microphones (i.e., receivers). Because of the special interest in spherical microphone arrays for DRIR measurement, the spherical coordinate system is considered for the description of the receivers. The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: SOFAConventions: SingleRoomDRIR, Datatype: FIR, RoomType: freefield with a mandatory attribute RoomDescription. * Data: The amount of the receivers varies, thus, the size of Data.IR is [M R N]. Only one sampling rate is allowed, thus SamplingRate is [1] (in Hz). * Source: The position and the orientation of the source may vary by providing SourcePosition, SourceUp, SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and * EmitterView are omitted. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is spherical and unit is “degrees, degrees, meter”. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. * An additional rotation of the listener is not considered, thus, ListenerRotation is not provided. * For each measurement, an ID and the time stamp is considered, with MeasurementID as [M] and MeasurementTimeCreated as [M]. The corresponding CDL file is provided in the “Conventions” directory of the SOFA package. cb3f3cf7df0d3c6d806d056dccd4aee8165c1222 0 7 10 2013-05-17T06:12:49Z Isfmiho 3 Created page with "discussion continues..." wikitext text/x-wiki discussion continues... f84150ae7884b9c0b613b2600bb814c568b94aee 0 8 11 2013-05-17T06:13:09Z Isfmiho 3 Created page with "discussion continues..." wikitext text/x-wiki discussion continues... f84150ae7884b9c0b613b2600bb814c568b94aee 0 9 16 2013-05-17T08:13:22Z Isfmiho 3 Created page with "This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free ..." wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. The corresponding CDL file is provided in the Conventions directory of the SOFA package. {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions|| SOFA||rm|| || |- |GLOBAL_Version|| 0.3|| rm || || |- |GLOBAL_SOFAConventions ||SimpleFreeFieldHRIR|| rm |||| |- |GLOBAL_SOFAConventionsVersion|| 0.1|| m || || |- |GLOBAL_APIName|| *|| rm || || Insert the API Name here |- |GLOBAL_APIVersion|| * ||rm || || Insert the API Version here |- |GLOBAL_ApplicationName |||| m |||| |- |GLOBAL_ApplicationVersion |||| m |||| |- |GLOBAL_AuthorContact |||| m |||| |- |GLOBAL_License No license provided, ask the author for permission|||| m |||| |- |GLOBAL_Organization |||| m |||| |- |GLOBAL_DatabaseName |||| m |||| |- |GLOBAL_SubjectID |||| m |||| |- |GLOBAL_RoomType|| free field ||m |||| |- |GLOBAL_DataType|| FIR ||m |||| |- |GLOBAL_History |||||||| |- |GLOBAL_Comment |||||||| |- |GLOBAL_DatabaseTimeCreated ||*|| m |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified ||* ||m |||| will be updated each time when saving |- |I|| 1|| rm|| I || |- |I_LongName|| singleton dimension|| rm || || |- |R|| 2|| rm|| R || |- |R_LongName|| number of receivers|| rm |||| |- |E|| 1|| rm|| E || |- |E_LongName ||number of emitters|| rm |||| |- |N || - || m ||N|| |- |N_LongName|| time ||m|| || |- |N_Units|| samples|| m || || |- |M|| - || m|| M || |- |M_LongName|| number of measurements|| rm |||| |- |C|| 3|| rm|| C|| |- |C_LongName|| coordinate triplet|| rm |||| |- |ListenerPosition|| [1 0 0] || m|| IC, MC || |- ListenerPosition_Type|| cartesian|| m || |- |ListenerPosition_Units meter|||| m|||| |- |ListenerUp|| [1.2 0 1]|| m ||IC, MC|| |- |ListenerUp_Type|| cartesian|| m |||| |- |ListenerUp_Units|| meter|| m |||| |- |ListenerView ||[0 0 0]|| m|| IC, MC || |- |ListenerView_Type|| cartesian|| m |||| |- |ListenerView_Units ||meter|| m |||| |- |ListenerRotation ||[0 0 0]|| m|| IC, MC || |- |- |ListenerRotation_Type|| din9300|| m |||| |- |ListenerRotation_Units ||degrees ||m |||| |- |ReceiverPosition ||[0 -0.09 0; 0 0.09 0]|| m|| rCI, rCM || |- |ReceiverPosition_Type|| cartesian ||m |||| |- |ReceiverPosition_Units ||meter ||m |||| |- |SourcePosition|| [0 0 0]|| m ||IC, MC || |- |SourcePosition_Type|| cartesian|| m |||| |- |SourcePosition_Units|| meter ||m |||| |- |SourceUp ||[0 0 1] ||m ||IC, MC || |- |SourceUp_Type ||cartesian|| m|||| |- |SourceUp_Units|| meter ||m|||| |- |SourceView ||[1 0 0] ||m|| IC, MC || |- |SourceView_Type ||cartesian|| m |||| |- |SourceView_Units ||meter|| m |||| |- |EmitterPosition|| [0 0 0] ||m ||eCI, eCM || |- |EmitterPosition_Type ||cartesian|| m |||| |- |EmitterPosition_Units ||meter|| m |||| |- |Data.IR ||[1 1]|| m ||mRn || |- |Data.SamplingRate|| 48000|| m|| I || |- |Data.SamplingRate_Units ||hertz|| m|| || |} 60383470f4bce21da6372e23000c60012d16be06 17 16 2013-05-17T08:13:47Z Isfmiho 3 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. The corresponding CDL file is provided in the Conventions directory of the SOFA package. {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions|| SOFA||rm|| || |- |GLOBAL_Version|| 0.3|| rm || || |- |GLOBAL_SOFAConventions ||SimpleFreeFieldHRIR|| rm |||| |- |GLOBAL_SOFAConventionsVersion|| 0.1|| m || || |- |GLOBAL_APIName|| *|| rm || || Insert the API Name here |- |GLOBAL_APIVersion|| * ||rm || || Insert the API Version here |- |GLOBAL_ApplicationName |||| m |||| |- |GLOBAL_ApplicationVersion |||| m |||| |- |GLOBAL_AuthorContact |||| m |||| |- |GLOBAL_License No license provided, ask the author for permission|||| m |||| |- |GLOBAL_Organization |||| m |||| |- |GLOBAL_DatabaseName |||| m |||| |- |GLOBAL_SubjectID |||| m |||| |- |GLOBAL_RoomType|| free field ||m |||| |- |GLOBAL_DataType|| FIR ||m |||| |- |GLOBAL_History |||||||| |- |GLOBAL_Comment |||||||| |- |GLOBAL_DatabaseTimeCreated ||*|| m |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified ||* ||m |||| will be updated each time when saving |- |I|| 1|| rm|| I || |- |I_LongName|| singleton dimension|| rm || || |- |R|| 2|| rm|| R || |- |R_LongName|| number of receivers|| rm |||| |- |E|| 1|| rm|| E || |- |E_LongName ||number of emitters|| rm |||| |- |N || - || m ||N|| |- |N_LongName|| time ||m|| || |- |N_Units|| samples|| m || || |- |M|| - || m|| M || |- |M_LongName|| number of measurements|| rm |||| |- |C|| 3|| rm|| C|| |- |C_LongName|| coordinate triplet|| rm |||| |- |ListenerPosition|| [1 0 0] || m|| IC, MC || |- |ListenerPosition_Type|| cartesian|| m || || |- |ListenerPosition_Units meter|||| m|||| |- |ListenerUp|| [1.2 0 1]|| m ||IC, MC|| |- |ListenerUp_Type|| cartesian|| m |||| |- |ListenerUp_Units|| meter|| m |||| |- |ListenerView ||[0 0 0]|| m|| IC, MC || |- |ListenerView_Type|| cartesian|| m |||| |- |ListenerView_Units ||meter|| m |||| |- |ListenerRotation ||[0 0 0]|| m|| IC, MC || |- |- |ListenerRotation_Type|| din9300|| m |||| |- |ListenerRotation_Units ||degrees ||m |||| |- |ReceiverPosition ||[0 -0.09 0; 0 0.09 0]|| m|| rCI, rCM || |- |ReceiverPosition_Type|| cartesian ||m |||| |- |ReceiverPosition_Units ||meter ||m |||| |- |SourcePosition|| [0 0 0]|| m ||IC, MC || |- |SourcePosition_Type|| cartesian|| m |||| |- |SourcePosition_Units|| meter ||m |||| |- |SourceUp ||[0 0 1] ||m ||IC, MC || |- |SourceUp_Type ||cartesian|| m|||| |- |SourceUp_Units|| meter ||m|||| |- |SourceView ||[1 0 0] ||m|| IC, MC || |- |SourceView_Type ||cartesian|| m |||| |- |SourceView_Units ||meter|| m |||| |- |EmitterPosition|| [0 0 0] ||m ||eCI, eCM || |- |EmitterPosition_Type ||cartesian|| m |||| |- |EmitterPosition_Units ||meter|| m |||| |- |Data.IR ||[1 1]|| m ||mRn || |- |Data.SamplingRate|| 48000|| m|| I || |- |Data.SamplingRate_Units ||hertz|| m|| || |} 744ea5a88453d6ac03c1ed581ecd5416ac7b81ed 18 17 2013-05-17T08:16:11Z Isfmiho 3 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. The corresponding CDL file is provided in the Conventions directory of the SOFA package. {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_LicenseNo license provided, ask the author for permission||||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 1c18e48881d49597261fbfa5d54baf057ad17712 19 18 2013-05-17T08:32:11Z Isfmiho 3 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. The corresponding CDL file is provided in the Conventions directory of the SOFA package. [[File:http://sofaconventions.org/SimpleFreeFieldHRTF.png]] {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_LicenseNo license provided, ask the author for permission||||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 55b0f988b833022e973b4baa87fe66ec1e8460ad 20 19 2013-05-17T08:32:41Z Isfmiho 3 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. The corresponding CDL file is provided in the Conventions directory of the SOFA package. [[File:SimpleFreeFieldHRTF.png]] {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_LicenseNo license provided, ask the author for permission||||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} b5c4b32b450ca04a008258256bc936a642e3b031 21 20 2013-05-17T08:34:24Z Isfmiho 3 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. The corresponding CDL file is provided in the Conventions directory of the SOFA package. [[http://sofaconventions.org/SimpleFreeFieldHRTF.png Bild]] {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_LicenseNo license provided, ask the author for permission||||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 62fdcb1a492230f6d853948d7674ac1bfa27b7ed 40 21 2013-05-17T09:54:59Z Petibub 4 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. [[http://sofaconventions.org/SimpleFreeFieldHRTF.png Bild]] {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_LicenseNo license provided, ask the author for permission||||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 8842bfbadd9879ad36661e51b02916434600ec86 0 10 24 2013-05-17T09:23:12Z Petibub 4 Created page with " == General == Head-related transfer functions (HRTFs) describe the spatial filtering of the incoming sound due to the listener's anatomy. HRTFs are crucially important for ..." wikitext text/x-wiki == General == Head-related transfer functions (HRTFs) describe the spatial filtering of the incoming sound due to the listener's anatomy. HRTFs are crucially important for the binaural reproduction of virtual acoustics. HRTFs have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The **spatially oriented format for acoustics (SOFA)** aims at representing spatial data in a general way, allowing to store not only HRTFs but also more complex data, e.g., directional room impulse responses (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available HRTFs were those of a dummy-head microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, HRTFs for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The HRTFs are provided as impulse responses (IRs) with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available HRTFs measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The HRTFs are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other HRTF/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural HRTF measurement setups use only two microphones to record the left and right ear signals. However, HRTF/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal HRTF measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical HRTF measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, HRTFs were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An HRTF file format should thus consider even such parameters. == What SOFA provides == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an impulse response, IR) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, HRTFs have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an HRTF corresponds to a predefined direction used in the measurements. While the representation of HRTFs from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing HRTFs only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an HRTF matrix and additional matrices describing the direction of the corresponding HRTF, thus, allowing to represent HRTFs from any direction. In that formats, HRTFs from each listener are stored in a separate file. In the database storing the HRTFs as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those HRTFs are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to HRTFs, allowing to store HRTFs of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The HRTFs measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. b3dfdbb3a9c12b4b1dac917fcf725a01d184e936 25 24 2013-05-17T09:23:39Z Petibub 4 /* General */ wikitext text/x-wiki == General == Head-related transfer functions (HRTFs) describe the spatial filtering of the incoming sound due to the listener's anatomy. HRTFs are crucially important for the binaural reproduction of virtual acoustics. HRTFs have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only HRTFs but also more complex data, e.g., directional room impulse responses (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available HRTFs were those of a dummy-head microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, HRTFs for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The HRTFs are provided as impulse responses (IRs) with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available HRTFs measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The HRTFs are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other HRTF/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural HRTF measurement setups use only two microphones to record the left and right ear signals. However, HRTF/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal HRTF measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical HRTF measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, HRTFs were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An HRTF file format should thus consider even such parameters. == What SOFA provides == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an impulse response, IR) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, HRTFs have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an HRTF corresponds to a predefined direction used in the measurements. While the representation of HRTFs from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing HRTFs only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an HRTF matrix and additional matrices describing the direction of the corresponding HRTF, thus, allowing to represent HRTFs from any direction. In that formats, HRTFs from each listener are stored in a separate file. In the database storing the HRTFs as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those HRTFs are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to HRTFs, allowing to store HRTFs of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The HRTFs measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. b37e2ac7aa4306675a5c64dc3517938ca8445a09 26 25 2013-05-17T09:24:28Z Petibub 4 /* What SOFA provides */ wikitext text/x-wiki == General == Head-related transfer functions (HRTFs) describe the spatial filtering of the incoming sound due to the listener's anatomy. HRTFs are crucially important for the binaural reproduction of virtual acoustics. HRTFs have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only HRTFs but also more complex data, e.g., directional room impulse responses (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available HRTFs were those of a dummy-head microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, HRTFs for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The HRTFs are provided as impulse responses (IRs) with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available HRTFs measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The HRTFs are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other HRTF/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural HRTF measurement setups use only two microphones to record the left and right ear signals. However, HRTF/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal HRTF measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical HRTF measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, HRTFs were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An HRTF file format should thus consider even such parameters. == What SOFA provides == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an impulse response, IR) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, HRTFs have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an HRTF corresponds to a predefined direction used in the measurements. While the representation of HRTFs from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing HRTFs only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an HRTF matrix and additional matrices describing the direction of the corresponding HRTF, thus, allowing to represent HRTFs from any direction. In that formats, HRTFs from each listener are stored in a separate file. In the database storing the HRTFs as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those HRTFs are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to HRTFs, allowing to store HRTFs of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The HRTFs measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 3c5ffcfd030d82cb84d40cbc5b3d0fd19332a598 32 26 2013-05-17T09:27:50Z Petibub 4 Petibub moved page [[More general information on SOFA]] to [[General information on SOFA]] wikitext text/x-wiki == General == Head-related transfer functions (HRTFs) describe the spatial filtering of the incoming sound due to the listener's anatomy. HRTFs are crucially important for the binaural reproduction of virtual acoustics. HRTFs have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only HRTFs but also more complex data, e.g., directional room impulse responses (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available HRTFs were those of a dummy-head microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, HRTFs for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The HRTFs are provided as impulse responses (IRs) with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available HRTFs measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The HRTFs are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other HRTF/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural HRTF measurement setups use only two microphones to record the left and right ear signals. However, HRTF/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal HRTF measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical HRTF measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, HRTFs were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An HRTF file format should thus consider even such parameters. == What SOFA provides == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an impulse response, IR) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, HRTFs have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an HRTF corresponds to a predefined direction used in the measurements. While the representation of HRTFs from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing HRTFs only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an HRTF matrix and additional matrices describing the direction of the corresponding HRTF, thus, allowing to represent HRTFs from any direction. In that formats, HRTFs from each listener are stored in a separate file. In the database storing the HRTFs as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those HRTFs are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to HRTFs, allowing to store HRTFs of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The HRTFs measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 3c5ffcfd030d82cb84d40cbc5b3d0fd19332a598 0 11 28 2013-05-17T09:25:53Z Petibub 4 Created page with "* [[SOFA specifications v0.1|Specifications v0.1]] * [[SOFA specifications v0.2|Specifications v0.2]] * [[SOFA specifications v0.3|Specifications v0.3]]" wikitext text/x-wiki * [[SOFA specifications v0.1|Specifications v0.1]] * [[SOFA specifications v0.2|Specifications v0.2]] * [[SOFA specifications v0.3|Specifications v0.3]] 5acf72c0a2fc36aa76726314431ea894182f53f7 41 28 2013-05-17T09:56:33Z Petibub 4 wikitext text/x-wiki * [[SOFA specifications v0.1|Specifications v0.1]] * [[SOFA specifications v0.2|Specifications v0.2]] * [[http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download|Specifications v0.3]] 9ded674b025a3d79fc61ee2278cb49b3e49fc8f7 42 41 2013-05-17T09:57:02Z Petibub 4 wikitext text/x-wiki * [[SOFA specifications v0.1|Specifications v0.1]] * [[SOFA specifications v0.2|Specifications v0.2]] * [[http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download |Specifications v0.3]] 33ac61e091b32a5850c4200acb2742c1d729a1bf 43 42 2013-05-17T09:57:25Z Petibub 4 wikitext text/x-wiki * [[SOFA specifications v0.1|Specifications v0.1]] * [[SOFA specifications v0.2|Specifications v0.2]] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Specifications v0.3] 88c0ac1c0e0ed823cf8bdbec9fdafc9305efe58c 44 43 2013-05-17T09:59:30Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Specifications version 0.1 (as presented at the AES Convention 2013 in Rom)] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Specifications version 0.2] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Specifications version 0.3] 42b90878ecbdacdad97f7bbe06f779dbd5561103 45 44 2013-05-17T10:00:10Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Specifications version 0.3] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Specifications version 0.2] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Specifications version 0.1 (as presented at the AES Convention 2013 in Rom)] f051f7a1b4af2cda9da99e15ed0cd5c9be156cc7 0 12 30 2013-05-17T09:26:46Z Petibub 4 Petibub moved page [[SOFA Conventions]] to [[SOFA conventions]] wikitext text/x-wiki #REDIRECT [[SOFA conventions]] fc889bd67550091045d35df9b98784b2b6fff39c 0 13 33 2013-05-17T09:27:50Z Petibub 4 Petibub moved page [[More general information on SOFA]] to [[General information on SOFA]] wikitext text/x-wiki #REDIRECT [[General information on SOFA]] 8d4a662d040fbe4c2a373be8d20eea0a940d4013 0 14 37 2013-05-17T09:44:57Z Petibub 4 Created page with " == Common Data Form Language (CDL) == SOFA conventions can be implemented without any programming by using CDL as suggested for netCDF. CDL files allow for a platform-indepe..." wikitext text/x-wiki == Common Data Form Language (CDL) == SOFA conventions can be implemented without any programming by using CDL as suggested for netCDF. CDL files allow for a platform-independent interpretation of specifications and can be compiled to a binary netCDF file using the ncgen tool from the netCDF package: ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl The binaries of the nc-tools are available at the Unidata. == HDF5View == SOFA files can be loaded and edited in the HDFView - a viewer for HDF5 files. Note that SOFA files are based on netCDF-4, which is based on HDF5. f4a28c726146526d1a219b1e182e9519ca9f1bc7 0 15 38 2013-05-17T09:47:21Z Petibub 4 Created page with "Here we provide the list of APIs available for SOFA. * https://sourceforge.net/projects/sofacoustics/" wikitext text/x-wiki Here we provide the list of APIs available for SOFA. * https://sourceforge.net/projects/sofacoustics/ 8861ae7a4ca120ef48f63df1b6b99f94583e9f55 46 38 2013-05-17T10:01:53Z Petibub 4 wikitext text/x-wiki Here we provide the list of APIs available for SOFA. * API for Matlab and Octave: https://sourceforge.net/projects/sofacoustics/ e6e707745c2660104cf241b61f05dcf076adf811 0 16 48 2013-05-17T10:15:43Z Petibub 4 Created page with "== Main == * '''Piotr Majdak''' (Acoustics Research Institute, Austrian Academy of Sciences): project leader * '''Hagen Wierstorf''' (Telekom Innovation Laboratories, Techn..." wikitext text/x-wiki == Main == * '''Piotr Majdak''' (Acoustics Research Institute, Austrian Academy of Sciences): project leader * '''Hagen Wierstorf''' (Telekom Innovation Laboratories, Technical University of Berlin): one of the project initiators, Octave support * '''Michael Mihocic''' (Acoustics Research Institute, Austrian Academy of Sciences): Matlab support, website support * '''Markus Noisternig''' (UMR STMS IRCAM-CNRS-UPMC): specifications * '''Matthieu Parmentier''' (France Television): standardization == Further support: == * '''Rozenn Nicol''' (Orange Labs, France Telecom, Lannion, France) * '''Agnieszka Roginska''' (Music Technology, New York University, NY, USA) * '''Harald Ziegelwanger''' (Acoustics Research Institute, Austrian Academy of Sciences) * '''Yôiti Suzuki (Research''' Institute of Electrical Communication, Tohoku University) * '''Kanji Watanabe''' (Faculty of Engineering, Akita Prefectural University) Also many thanks go to the '''AES standardization team''' for their support. ad0eddecf305c8ff98f68dadc6c54bb4307f8e1b 0 1 51 50 2013-05-17T10:22:54Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] * [[Files (HRTFs, BRIRs, DRIRs)|Files]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] d455d7cbab429239c6317a93c9715d755e6ba3cc 52 51 2013-05-17T10:23:23Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like the head-related transfer functions or direction room impulse responses. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] 8e64fc0042d2a98eb51dffb5843a6653a22d778b 56 52 2013-05-17T11:58:09Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like head-related transfer functions (HRTFs) and binaural or directional room impulse responses (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] 8bf68a70162cc852cd0b6cadb308ead7086bab7b 57 56 2013-05-17T12:01:07Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing spatially oriented acoustic data like head-related transfer functions (HRTFs) and binaural or directional room impulse responses (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing HRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] c183acc34097fe88a3327e787d4dc62bcf7d61ba 76 57 2013-05-17T13:10:40Z Isfmiho 3 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room impulse responses (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files ([http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] 6b25e2f70026983e7d17a17cce4308e0b5baae86 77 76 2013-05-17T13:11:23Z Isfmiho 3 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room impulse responses (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] 0c5480a73f0781b3c3bafc7c255819f49e955afc 0 17 53 2013-05-17T10:24:01Z Petibub 4 Created page with "Here we will write how to get the SOFA files...." wikitext text/x-wiki Here we will write how to get the SOFA files.... 35c35f42ff85f5090777c4440cf678d7ce7155af 55 53 2013-05-17T11:55:13Z Petibub 4 wikitext text/x-wiki This is a preliminary list of HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs These files can be accessed by downloading them. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA files). 4218ac7a9e574d24cc5e28c8b7ed138a90cd1411 58 55 2013-05-17T12:01:43Z Petibub 4 wikitext text/x-wiki This is a preliminary list of HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs These files can be accessed by downloading them. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA files). 4473ba1db1df8f4353e94baec58c8757d6dbbb69 59 58 2013-05-17T12:02:18Z Petibub 4 wikitext text/x-wiki This is a preliminary list of HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs These files can be accessed by downloading them. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). c3d08c99816b0521a75618f6df93d8953d6dbe57 0 9 54 40 2013-05-17T10:34:20Z Petibub 4 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. [[http://sofaconventions.org/SimpleFreeFieldHRTF.png Bild]] {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 4d708a25c3ba10b25f6d7e058c5104621b0824b4 63 54 2013-05-17T12:26:46Z Petibub 4 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. [[http://sofaconventions.org/SimpleFreeFieldHRTF.png Bild]] {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute ** GLOBAL_: the metadata is a global attribute ** X_Y: the metadata is an attribute Y of the variable X ** Data.X: structure of the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see Specifications for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) beb2e10b69921a84dd3b8a59cb2e082fda1aeca8 64 63 2013-05-17T12:28:23Z Petibub 4 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. [[http://sofaconventions.org/SimpleFreeFieldHRTF.png Bild]] {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see Specifications for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 7dc374ac1d06318d21933ec799e074865cc72732 65 64 2013-05-17T12:30:05Z Petibub 4 wikitext text/x-wiki This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. [[http://sofaconventions.org/SimpleFreeFieldHRTF.png Bild]] {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 5d6bfa8a51f7c25a3e29bd40f909e2d46d7dec71 0 5 60 39 2013-05-17T12:10:39Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions ==Stable Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. Measured data exist and the description must be fixed in order to create publicly available SOFA files and software. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. ==Discussion & Requests== Here we discuss suggestions from the peer group * Item 1(Author 1) * Item 2 (Author 2) d62e2744f16d80053b03ad85b1f05d7a5d996847 66 60 2013-05-17T12:33:23Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available ==Stable Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. Measured data exist and the description must be fixed in order to create publicly available SOFA files and software. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. ==Discussion & Requests== Here we discuss suggestions from the peer group * Item 1(Author 1) * Item 2 (Author 2) 46011973ddd31eb80304764d396bc4fa0b98154f 78 66 2013-05-17T13:33:32Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Item 1(Author 1) * Item 2 (Author 2) == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 2818694739dd91ed6aba2b3d06f59a235de413c9 85 78 2013-05-17T14:49:32Z Petibub 4 /* Unsorted topics */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Headphone transfer functions: data exist, need more information on metadata * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 89d1ab9df6b8b3ae8d32853752e4f337bcc01280 0 11 61 45 2013-05-17T12:12:04Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Specifications version 0.3] * [[Discussion]]: discuss the details of improvements you would like to see in the next version. * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Specifications version 0.2] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Specifications version 0.1 (as presented at the AES Convention 2013 in Rom)] be6e79bb7fcf5948bc41f43dfc97686c0cbd083e 62 61 2013-05-17T12:13:45Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Specifications version 0.3] * [[Specifications discussion |Discussion]]: discuss with us the details of improvements you would like to see in the next SOFA version. * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Specifications version 0.2] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Specifications version 0.1 (as presented at the AES Convention 2013 in Rom)] ed84753cb5dd5da106e306780e24b36f44bcb072 80 62 2013-05-17T13:38:44Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Download specifications version 0.3] * [[Proposal 0.4 | Draft proposal for specifications version 0.4]]: discuss with us the details of improvements you would like to see in the next SOFA version. * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Specifications version 0.2] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Specifications version 0.1 (as presented at the AES Convention 2013 in Rom)] 7cc9517f0e4b6fa42821084c42f1be1ebbb42bef 0 10 67 32 2013-05-17T12:34:43Z Petibub 4 wikitext text/x-wiki == General == Head-related transfer functions (HRTFs) describe the spatial filtering of the incoming sound due to the listener's anatomy. HRTFs are crucially important for the binaural reproduction of virtual acoustics. HRTFs have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only HRTFs but also more complex data, e.g., directional room impulse responses (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available HRTFs were those of a dummy-head microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, HRTFs for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The HRTFs are provided as impulse responses (IRs) with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available HRTFs measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The HRTFs are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other HRTF/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural HRTF measurement setups use only two microphones to record the left and right ear signals. However, HRTF/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal HRTF measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical HRTF measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, HRTFs were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An HRTF file format should thus consider even such parameters. == Aim of SOFA == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an impulse response, IR) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, HRTFs have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an HRTF corresponds to a predefined direction used in the measurements. While the representation of HRTFs from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing HRTFs only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an HRTF matrix and additional matrices describing the direction of the corresponding HRTF, thus, allowing to represent HRTFs from any direction. In that formats, HRTFs from each listener are stored in a separate file. In the database storing the HRTFs as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those HRTFs are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to HRTFs, allowing to store HRTFs of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The HRTFs measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 9dfb9d4b46cd408e062e3b4829b7777247bae6e4 72 67 2013-05-17T13:01:11Z Isfmiho 3 wikitext text/x-wiki == General == [http://en.wikipedia.org/wiki/Head-related_transfer_function Head-related transfer functions (HRTFs)] describe the spatial filtering of the incoming sound due to the listener's anatomy. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are crucially important for the binaural reproduction of virtual acoustics. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] but also more complex data, e.g., directional room impulse responses (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were those of a dummy-head microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are provided as impulse responses (IRs) with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement setups use only two microphones to record the left and right ear signals. However, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] file format should thus consider even such parameters. == Aim of SOFA == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an impulse response, IR) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] corresponds to a predefined direction used in the measurements. While the representation of [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] matrix and additional matrices describing the direction of the corresponding [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF], thus, allowing to represent [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from any direction. In that formats, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from each listener are stored in a separate file. In the database storing the [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] , allowing to store [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. d2191e944d59c594ddafe5e377fdd709841a9890 73 72 2013-05-17T13:03:45Z Isfmiho 3 wikitext text/x-wiki == General == [http://en.wikipedia.org/wiki/Head-related_transfer_function Head-related transfer functions (HRTFs)] describe the spatial filtering of the incoming sound due to the listener's anatomy. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are crucially important for the binaural reproduction of virtual acoustics. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] but also more complex data, e.g., [http://en.wikipedia.org/wiki/Impulse_response directional room impulse responses] (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were those of a dummy-head microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are provided as [http://en.wikipedia.org/wiki/Impulse_response impulse responses (IRs)] with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement setups use only two microphones to record the left and right ear signals. However, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] file format should thus consider even such parameters. == Aim of SOFA == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an [http://en.wikipedia.org/wiki/Impulse_response impulse response, IR]) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] corresponds to a predefined direction used in the measurements. While the representation of [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] matrix and additional matrices describing the direction of the corresponding [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF], thus, allowing to represent [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from any direction. In that formats, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from each listener are stored in a separate file. In the database storing the [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] , allowing to store [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 3f0eb71ee48df73582bc3c78d27ffd670d6e61fc 75 73 2013-05-17T13:06:47Z Isfmiho 3 wikitext text/x-wiki == General == [http://en.wikipedia.org/wiki/Head-related_transfer_function Head-related transfer functions (HRTFs)] describe the spatial filtering of the incoming sound due to the listener's anatomy. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are crucially important for the binaural reproduction of virtual acoustics. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] but also more complex data, e.g., [http://en.wikipedia.org/wiki/Impulse_response directional room impulse responses] (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were those of a [http://en.wikipedia.org/wiki/Dummy_head_recording dummy-head] microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are provided as [http://en.wikipedia.org/wiki/Impulse_response impulse responses (IRs)] with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement setups use only two microphones to record the left and right ear signals. However, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] file format should thus consider even such parameters. == Aim of SOFA == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an [http://en.wikipedia.org/wiki/Impulse_response impulse response, IR]) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] corresponds to a predefined direction used in the measurements. While the representation of [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] matrix and additional matrices describing the direction of the corresponding [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF], thus, allowing to represent [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from any direction. In that formats, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from each listener are stored in a separate file. In the database storing the [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] , allowing to store [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 483c3209105db7ec907b0c96c150140c5dc8f190 0 16 68 48 2013-05-17T12:49:24Z Petibub 4 wikitext text/x-wiki == Main == * '''Piotr Majdak''' (Acoustics Research Institute, Austrian Academy of Sciences): project leader * '''Hagen Wierstorf''' (Telekom Innovation Laboratories, Technical University of Berlin): one of the project initiators, Octave support * '''Michael Mihocic''' (Acoustics Research Institute, Austrian Academy of Sciences): Matlab support, website support * '''Markus Noisternig''' (UMR STMS IRCAM-CNRS-UPMC): specifications * '''Matthieu Parmentier''' (France Television): standardization == Acknowledgments: == * '''Rozenn Nicol''' (Orange Labs, France Telecom, Lannion, France) * '''Agnieszka Roginska''' (Music Technology, New York University, NY, USA) * '''Harald Ziegelwanger''' (Acoustics Research Institute, Austrian Academy of Sciences) * '''Yôiti Suzuki (Research''' Institute of Electrical Communication, Tohoku University) * '''Kanji Watanabe''' (Faculty of Engineering, Akita Prefectural University) Also many thanks go to the '''AES standardization team''' for their support. == Contact: == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message. c37d0c2ee12da4c4edfc1a7221b4723e627021fa 69 68 2013-05-17T12:52:56Z Petibub 4 wikitext text/x-wiki == Main == * '''Piotr Majdak''' (Acoustics Research Institute, Austrian Academy of Sciences): project leader * '''Hagen Wierstorf''' (Telekom Innovation Laboratories, Technical University of Berlin): one of the project initiators, Octave support * '''Michael Mihocic''' (Acoustics Research Institute, Austrian Academy of Sciences): Matlab support, website support * '''Markus Noisternig''' (UMR STMS IRCAM-CNRS-UPMC): specifications * '''Matthieu Parmentier''' (France Television): standardization == Acknowledgments: == * '''Rozenn Nicol''' (Orange Labs, France Telecom, Lannion, France) * '''Agnieszka Roginska''' (Music Technology, New York University, NY, USA) * '''Harald Ziegelwanger''' (Acoustics Research Institute, Austrian Academy of Sciences) * '''Yôiti Suzuki''' (Research Institute of Electrical Communication, Tohoku University) * '''Kanji Watanabe''' (Faculty of Engineering, Akita Prefectural University) Also many thanks go to the '''AES standardization team''' for their support. == Contact: == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message. 5245073a62b954a211470878a67b7a114d2f5ca9 70 69 2013-05-17T12:54:35Z 129.102.66.18 0 wikitext text/x-wiki == Main == * '''Piotr Majdak''' (Acoustics Research Institute, Austrian Academy of Sciences): project leader * '''Hagen Wierstorf''' (Telekom Innovation Laboratories, Technical University of Berlin): one of the project initiators, Octave support * '''Michael Mihocic''' (Acoustics Research Institute, Austrian Academy of Sciences): Matlab support, website support * '''Markus Noisternig''' (UMR STMS IRCAM-CNRS-UPMC): specifications, standardization * '''Matthieu Parmentier''' (France Television): standardization == Acknowledgments: == * '''Rozenn Nicol''' (Orange Labs, France Telecom, Lannion, France) * '''Agnieszka Roginska''' (Music Technology, New York University, NY, USA) * '''Harald Ziegelwanger''' (Acoustics Research Institute, Austrian Academy of Sciences) * '''Yôiti Suzuki''' (Research Institute of Electrical Communication, Tohoku University) * '''Kanji Watanabe''' (Faculty of Engineering, Akita Prefectural University) Also many thanks go to the '''AES standardization team''' for their support. == Contact: == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message. f5baa3cce50ef9094af482c48a53fefd53532053 71 70 2013-05-17T13:00:51Z Petibub 4 wikitext text/x-wiki SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). * '''Piotr Majdak''' (Acoustics Research Institute, Austrian Academy of Sciences): project leader * '''Hagen Wierstorf''' (Telekom Innovation Laboratories, Technical University of Berlin): one of the project initiators, Octave support * '''Michael Mihocic''' (Acoustics Research Institute, Austrian Academy of Sciences): Matlab support, website support * '''Markus Noisternig''' (UMR STMS IRCAM-CNRS-UPMC): specifications, standardization * '''Matthieu Parmentier''' (France Television): standardization == Acknowledgments == * '''Rozenn Nicol''' (Orange Labs, France Telecom, Lannion, France) * '''Agnieszka Roginska''' (Music Technology, New York University, NY, USA) * '''Harald Ziegelwanger''' (Acoustics Research Institute, Austrian Academy of Sciences) * '''Yôiti Suzuki''' (Research Institute of Electrical Communication, Tohoku University) * '''Kanji Watanabe''' (Faculty of Engineering, Akita Prefectural University) Also many thanks go to the '''AES standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message. == References == J. Blauert, J. Braasch, J. Bucholz, H.S. Colburn, U. Jekosch, A. Kohlrausch, J. Mourjopoulos, V. Pulkki, A. Raake, "Aural assessment by means of binaural algorithms - The AABBA project -" Proceedings of ISSAR 2009: Binaural Processing and Spatial Hearing, 2nd International Symposium on Auditory and Audiological Research c1e10caf6bc881a605a99291926c0ca0e064203f 74 71 2013-05-17T13:06:31Z Petibub 4 wikitext text/x-wiki * '''Piotr Majdak''' (Acoustics Research Institute, Austrian Academy of Sciences): project leader * '''Hagen Wierstorf''' (Telekom Innovation Laboratories, Technical University of Berlin): one of the project initiators, Octave support * '''Michael Mihocic''' (Acoustics Research Institute, Austrian Academy of Sciences): Matlab support, website support * '''Markus Noisternig''' (UMR STMS IRCAM-CNRS-UPMC): specifications, standardization * '''Matthieu Parmentier''' (France Television): standardization SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Rozenn Nicol''' (Orange Labs, France Telecom, Lannion, France) * '''Agnieszka Roginska''' (Music Technology, New York University, NY, USA) * '''Harald Ziegelwanger''' (Acoustics Research Institute, Austrian Academy of Sciences) * '''Yôiti Suzuki''' (Research Institute of Electrical Communication, Tohoku University) * '''Kanji Watanabe''' (Faculty of Engineering, Akita Prefectural University) Also many thanks go to the '''AES standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 63bf0889cc671c11027dd4ec08edeedcbbfefb3e 79 74 2013-05-17T13:34:37Z Petibub 4 wikitext text/x-wiki * '''Piotr Majdak''' (Acoustics Research Institute, Austrian Academy of Sciences): project leader * '''Hagen Wierstorf''' (Telekom Innovation Laboratories, Technical University of Berlin): one of the project initiators, Octave support * '''Michael Mihocic''' (Acoustics Research Institute, Austrian Academy of Sciences): Matlab support, website support * '''Markus Noisternig''' (UMR STMS IRCAM-CNRS-UPMC): specifications, standardization * '''Matthieu Parmentier''' (France Television): standardization SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Rozenn Nicol''' (Orange Labs, France Telecom, Lannion, France) * '''Agnieszka Roginska''' (Music Technology, New York University, NY, USA) * '''Harald Ziegelwanger''' (Acoustics Research Institute, Austrian Academy of Sciences) * '''Yôiti Suzuki''' (Research Institute of Electrical Communication, Tohoku University) * '''Kanji Watanabe''' (Faculty of Engineering, Akita Prefectural University) Also many thanks go to the '''AES standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 9057b6305e15004c53c35b3ccad1799e8438f908 0 18 81 2013-05-17T13:41:54Z Petibub 4 Created page with "== Fix mandatory metadata == == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions ==" wikitext text/x-wiki == Fix mandatory metadata == == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == 1eff5034f70ddbec0d6010928221ec265f8ec8cc 82 81 2013-05-17T13:42:54Z Petibub 4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' == Fix mandatory metadata == == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == 69c84431200c9871102782a36d49570a840ec514 83 82 2013-05-17T14:00:49Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||time|||| || |- |N_Units||samples|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Unitsmeter|||||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.FIR||[1 1]||||mRn||Only mandatory when DatyType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DatyType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DatyType is FIR | == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == e49f947aac30c15f6347ad758a4db87680a5fd70 84 83 2013-05-17T14:34:00Z Petibub 4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||time|||| || |- |N_Units||samples|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Unitsmeter|||||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.FIR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == 53788b2f416f077681e2c65b584756278f0b4ac6 88 84 2013-05-17T15:01:47Z Petibub 4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||time|||| || |- |N_Units||samples|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Unitsmeter|||||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.FIR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == 8ebab449ce2f9f7656bb16602f0ac1e00e1e596f 92 88 2013-05-17T15:34:49Z Petibub 4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||time|||| || |- |N_Units||samples|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Unitsmeter|||||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.FIR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == == Fix the coordinate systems == 1c34c32c0db90b2cd8e8364ba1ecc2e180715b9d 1 19 86 2013-05-17T14:50:23Z Petibub 4 Created page with " == Headphone transfer functions: data exist, need more information on metadata == == Include anthropometric data == == Crosstalk cancellation filters == == Include calibratio..." wikitext text/x-wiki == Headphone transfer functions: data exist, need more information on metadata == == Include anthropometric data == == Crosstalk cancellation filters == == Include calibration data from the measurement == == Include room pictures == 376cf11eadf7b1fc01166f8f71f7c33c543d531f 87 86 2013-05-17T15:00:15Z Petibub 4 /* Headphone transfer functions: data exist, need more information on metadata */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data == == Crosstalk cancellation filters == == Include calibration data from the measurement == == Include room pictures == 7106c2b5dd72d439017b2c9c2522e216c9d26fbe 95 87 2013-05-17T15:51:18Z Petibub 4 /* Include room pictures */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data == == Crosstalk cancellation filters == == Include calibration data from the measurement == == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 5ccdb89076786d8322b6026d4a48edc6f118d03c 96 95 2013-05-17T15:56:50Z Petibub 4 wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data == == Crosstalk cancellation filters == == Include calibration data == == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 633f418b0abf55f0dcfcd80a52f3c8935a3bc775 97 96 2013-05-17T15:58:25Z Petibub 4 /* Include calibration data */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data == == Crosstalk cancellation filters == == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... b3cca980388c5eeb223d1eff2fe32b7117fa5768 98 97 2013-05-17T16:06:27Z Petibub 4 /* Include anthropometric data */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters == == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... f76b9b101a9da0e7223c29a333b737925f830dfa 99 98 2013-05-17T16:09:07Z Petibub 4 /* Crosstalk cancellation filters */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 9e96336340c863e80e008d080c19296092d0ee43 1 20 89 2013-05-17T15:06:57Z Petibub 4 Created page with "== Fix mandatory metadata == == Fix versioning of SOFA and conventions == For the moment, we have a version number for the SOFA specs and each conventions has its own version..." wikitext text/x-wiki == Fix mandatory metadata == == Fix versioning of SOFA and conventions == For the moment, we have a version number for the SOFA specs and each conventions has its own version number. This appears rather much, but gives us more freedom (formulate that!) == Fix if datatypes can change within conventions == When we say "conventions" do we mean a fixed data type? * yes: because it will be very easy for applications: they just have to check the conventions and the data type is fixed. On the other hand, we'll need a separate conventions for each datatype even though the measurement setup might have not changed. * no: we will have conventions which do not consider the datatype (=less conventions). On the other hand, each application has either to provide '''all''' datatypes or to check two things: conventions '''and''' datatype 087ec04eb5427975a829691f4d2fe63aa906bf81 90 89 2013-05-17T15:10:59Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki == Fix mandatory metadata == The table is in the main page. I used the following rules: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions In other words, my suggestion represents the minimal version of any conventions. Let's see if this is consistent... == Fix versioning of SOFA and conventions == For the moment, we have a version number for the SOFA specs and each conventions has its own version number. This appears rather much, but gives us more freedom (formulate that!) == Fix if datatypes can change within conventions == When we say "conventions" do we mean a fixed data type? * yes: because it will be very easy for applications: they just have to check the conventions and the data type is fixed. On the other hand, we'll need a separate conventions for each datatype even though the measurement setup might have not changed. * no: we will have conventions which do not consider the datatype (=less conventions). On the other hand, each application has either to provide '''all''' datatypes or to check two things: conventions '''and''' datatype 71144e8f4b8cc158980eef9c26d2c8abb272c3e7 91 90 2013-05-17T15:25:28Z Petibub 4 /* Datatype: Complex spectra */ new section wikitext text/x-wiki == Fix mandatory metadata == The table is in the main page. I used the following rules: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions In other words, my suggestion represents the minimal version of any conventions. Let's see if this is consistent... == Fix versioning of SOFA and conventions == For the moment, we have a version number for the SOFA specs and each conventions has its own version number. This appears rather much, but gives us more freedom (formulate that!) == Fix if datatypes can change within conventions == When we say "conventions" do we mean a fixed data type? * yes: because it will be very easy for applications: they just have to check the conventions and the data type is fixed. On the other hand, we'll need a separate conventions for each datatype even though the measurement setup might have not changed. * no: we will have conventions which do not consider the datatype (=less conventions). On the other hand, each application has either to provide '''all''' datatypes or to check two things: conventions '''and''' datatype == Datatype: Complex spectra == A new datatype has been requested, allowing to store complex spectra. While in general quite clear what to do, a few details require clarification: * Do data exist? Most of the data are saved as IRs and can be easily transformed to frequency domain on loading by the application. Data natively stored as spectra or special needs for storing data directly as spectra would help. * Most of the measured IRs are real-valued. Complex spectra introduce redundancy for those IRs, resulting in increase of the file size. This disadvantage might be small because of the compression available in SOFA. Another way to handle that would be to store only parts of the spectra. This issue should be clarified. The corresponding requester/researcher has been contacted. Waiting for response... 28d9478dcb186af6db11666dc180ece1a431def5 93 91 2013-05-17T15:36:58Z Petibub 4 /* Coordinate systems */ new section wikitext text/x-wiki == Fix mandatory metadata == The table is in the main page. I used the following rules: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions In other words, my suggestion represents the minimal version of any conventions. Let's see if this is consistent... == Fix versioning of SOFA and conventions == For the moment, we have a version number for the SOFA specs and each conventions has its own version number. This appears rather much, but gives us more freedom (formulate that!) == Fix if datatypes can change within conventions == When we say "conventions" do we mean a fixed data type? * yes: because it will be very easy for applications: they just have to check the conventions and the data type is fixed. On the other hand, we'll need a separate conventions for each datatype even though the measurement setup might have not changed. * no: we will have conventions which do not consider the datatype (=less conventions). On the other hand, each application has either to provide '''all''' datatypes or to check two things: conventions '''and''' datatype == Datatype: Complex spectra == A new datatype has been requested, allowing to store complex spectra. While in general quite clear what to do, a few details require clarification: * Do data exist? Most of the data are saved as IRs and can be easily transformed to frequency domain on loading by the application. Data natively stored as spectra or special needs for storing data directly as spectra would help. * Most of the measured IRs are real-valued. Complex spectra introduce redundancy for those IRs, resulting in increase of the file size. This disadvantage might be small because of the compression available in SOFA. Another way to handle that would be to store only parts of the spectra. This issue should be clarified. The corresponding requester/researcher has been contacted. Waiting for response... == Coordinate systems == Need to fix a few details: * In "spherical": Elevation angle vs. Zenith angle * Quaternions? a843d4b7296e2197a575597247ae11773963fcbe 0 21 94 2013-05-17T15:41:52Z Petibub 4 Created page with "This conventions aims at storing HRIRs and BRIRs and providing an information whether reflections have been involved in the measurement. The draft considers: As SimpleFree..." wikitext text/x-wiki This conventions aims at storing HRIRs and BRIRs and providing an information whether reflections have been involved in the measurement. The draft considers: As SimpleFreeFieldHRIR but the GLOBAL_RoomType is: * "free field": reflects SimpleFreeFieldHRIR * "reverberant": HRIRs measured in a reverberant space Additionally, GLOBAL_RoomDescription is mandatory. c46a299a0df88eba0abaa76cfdbd13b1ffd97700 4 22 100 2013-05-17T18:18:39Z Petibub 4 Created page with "Website Owner The Acoustics Research Institute of the Austrian Academy of Sciences Wohllebengasse 12-14 A-1040 Vienna, Austria, a research institute of the Austrian Academy o..." wikitext text/x-wiki Website Owner The Acoustics Research Institute of the Austrian Academy of Sciences Wohllebengasse 12-14 A-1040 Vienna, Austria, a research institute of the Austrian Academy of Sciences Legal entity under the special protection of the Federal Republic of Austria (BGBl 569/1921 idF BGBl I 130/2003) Dr. Ignaz Seipel-Platz 2, 1010 Vienna, Austria This website informs about the scientific activities of the Austrian Academy of Sciences, thus following the mission of the Academy to promote the sciences and humanities in every respect and in every field. 1735d39e4e59c508ab0eb6693c8220fa72e22b2e 0 17 101 59 2013-05-18T07:37:28Z 91.119.138.195 0 wikitext text/x-wiki This is a preliminary list of HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs These repositories provide SOFA files for download. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). 84fb19305aea914f144adcb9b99967fc06b515f4 1 19 102 99 2013-05-18T08:46:59Z 81.65.98.52 0 /* Include calibration data */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurment in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfert funciton of the measurement chain wihtout the measurment object present. In the case of the HRTF, this is the measured transfer function wihtout the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurments which use mutliple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independant of the head response and therefor an artifact of the measuremet system. In such a case, impulse responses should be provided for each speaker, with the microhpone oriented on-axis to the speaker. This can be performed with the measuremnet microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is alse necessary, consiting of a calibration measurment for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF mesurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independance of the mesuremnet system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilised. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 995848cdcd5a29aac7fb0a154131959aa6a0a3a0 103 102 2013-05-18T08:52:20Z 81.65.98.52 0 /* Crosstalk cancellation filters (CTCFs) */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore by no means universal. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurment in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfert funciton of the measurement chain wihtout the measurment object present. In the case of the HRTF, this is the measured transfer function wihtout the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurments which use mutliple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independant of the head response and therefor an artifact of the measuremet system. In such a case, impulse responses should be provided for each speaker, with the microhpone oriented on-axis to the speaker. This can be performed with the measuremnet microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is alse necessary, consiting of a calibration measurment for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF mesurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independance of the mesuremnet system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilised. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... be61703a4b751ca7ed4257dc6b56d63d90b279db 104 103 2013-05-18T08:56:48Z 81.65.98.52 0 /* Include calibration data */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore by no means universal. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 623040e09ca4da2dd9acecbc723057081411fe94 105 104 2013-05-18T09:07:31Z 81.65.98.52 0 /* Include calibration data */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore by no means universal. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... c3c84c6998a038c247f4b005aa105021a9ae44ec 106 105 2013-05-18T17:17:12Z Petibub 4 /* Crosstalk cancellation filters (CTCFs) */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 940191cf4048bc2e7b1bffd0c48e77265c58f7da 107 106 2013-05-18T17:28:37Z Petibub 4 /* Include calibration data */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". * Seems like we need a good definition of "raw", "processed", and "un-calibrated". Then we could provide an attribute, e.g., ProcessingState. Otherwise, we could use "ProcessingState" in the same way we use "Comments", namely, include a narrative description of the processing steps. Then we could write GLOBAL_ProcessingState = "Deconvolution with exp. sweep, windowing at ..., filtering at..." and so on. Applications which do not care, could ignore it; researchers who care could interpret it. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. * It seems like we would need to save the IRs from speaker(s) and microphone(s) together with other metadata like levels. Would it be sufficient to store that information in a separate SOFA file? Applications which do not care, would not have this ballast. Researchers who care, could use it to reproduce all post-processing steps. A new SOFA conventions for calibration would do - Does it make sense? == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 3c1ec5b8c10ef6dd9a4730f6fa639fb790319724 108 107 2013-05-21T10:58:23Z 193.171.195.36 0 wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs<ref>Testing the footnote extension</ref>. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". * Seems like we need a good definition of "raw", "processed", and "un-calibrated". Then we could provide an attribute, e.g., ProcessingState. Otherwise, we could use "ProcessingState" in the same way we use "Comments", namely, include a narrative description of the processing steps. Then we could write GLOBAL_ProcessingState = "Deconvolution with exp. sweep, windowing at ..., filtering at..." and so on. Applications which do not care, could ignore it; researchers who care could interpret it. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. * It seems like we would need to save the IRs from speaker(s) and microphone(s) together with other metadata like levels. Would it be sufficient to store that information in a separate SOFA file? Applications which do not care, would not have this ballast. Researchers who care, could use it to reproduce all post-processing steps. A new SOFA conventions for calibration would do - Does it make sense? == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... <references /> ea84b2c4770de4210e4fb1e0e813e7563ccd85f7 111 108 2013-05-21T11:41:49Z Ente 1 Reverted edits by [[Special:Contributions/193.171.195.36|193.171.195.36]] ([[User talk:193.171.195.36|talk]]) to last revision by [[User:Petibub|Petibub]] wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". * Seems like we need a good definition of "raw", "processed", and "un-calibrated". Then we could provide an attribute, e.g., ProcessingState. Otherwise, we could use "ProcessingState" in the same way we use "Comments", namely, include a narrative description of the processing steps. Then we could write GLOBAL_ProcessingState = "Deconvolution with exp. sweep, windowing at ..., filtering at..." and so on. Applications which do not care, could ignore it; researchers who care could interpret it. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. * It seems like we would need to save the IRs from speaker(s) and microphone(s) together with other metadata like levels. Would it be sufficient to store that information in a separate SOFA file? Applications which do not care, would not have this ballast. Researchers who care, could use it to reproduce all post-processing steps. A new SOFA conventions for calibration would do - Does it make sense? == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 3c1ec5b8c10ef6dd9a4730f6fa639fb790319724 122 111 2013-05-21T21:00:07Z Petibub 4 /* Include calibration data */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". * Seems like we need a good definition of "raw", "processed", and "un-calibrated". Then we could provide an attribute, e.g., ProcessingState. Otherwise, we could use "ProcessingState" in the same way we use "Comments", namely, include a narrative description of the processing steps. Then we could write GLOBAL_ProcessingState = "Deconvolution with exp. sweep, windowing at ..., filtering at..." and so on. Applications which do not care, could ignore it; researchers who care could interpret it. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. * It seems like we would need to save the IRs from speaker(s) and microphone(s) together with other metadata like levels. Would it be sufficient to store that information in a separate SOFA file? Applications which do not care, would not have this ballast. Researchers who care, could use it to reproduce all post-processing steps. A new SOFA conventions for calibration would do - Does it make sense? * Seems like level would be important. Data? What level? Why not simple calculate the level from the data? == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 82045774cbba5b3e9b743168b92abfa0d2334a75 0 16 109 79 2013-05-21T11:21:50Z Isfmiho 3 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): standardization SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Rozenn Nicol''' (Orange Labs, France Telecom, Lannion, France) * '''Agnieszka Roginska''' (Music Technology, New York University, NY, USA) * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]) * '''Yôiti Suzuki''' (Research Institute of Electrical Communication, Tohoku University) * '''Kanji Watanabe''' (Faculty of Engineering, Akita Prefectural University) Also many thanks go to the '''AES standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. cc945a4fa84ec6d936dd22e8cee5217f7fc60d13 110 109 2013-05-21T11:29:50Z Isfmiho 3 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): standardization SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''AES standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 2631cc6200fe91dc9afb417c3349bfa014eaefa0 118 110 2013-05-21T12:14:07Z Ente 1 Protected "[[People behind SOFA]]" (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite)) wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): standardization SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''AES standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 2631cc6200fe91dc9afb417c3349bfa014eaefa0 126 118 2013-05-22T06:58:49Z Isfmiho 3 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): standardization SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 3a99ac422fa581770e32070bee8bd6048f43bcd7 131 126 2013-05-23T14:35:07Z Petibub 4 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): standardization * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C+ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. a2a964474fa46c11e5e42c38a0dc7ad1516c008f 132 131 2013-05-23T14:42:18Z Noisternig 5 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): standardization * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. bc9c49218c4a1f23d5c64bee12c2bf520f79519d 133 132 2013-05-23T14:43:34Z Noisternig 5 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): standardization * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 87697b997f7e810e39bd0d42fc8d3088c4d52154 134 133 2013-05-23T14:46:39Z Noisternig 5 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): '''[http://www.aes.org/ AES] standardization''" * ""Bruce Olson, AESSC Chair"": '''[http://www.aes.org/ AES] standardization committee chair''" * ""Mark Yonge, AESSC Secretary"": '''[http://www.aes.org/ AES] standardization committee secretary''" * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 3895edf1f054ae069069618432487d6eddb2e185 135 134 2013-05-23T14:48:14Z Noisternig 5 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): '''[http://www.aes.org/ AES] standardization''' * '''Bruce Olson, AESSC Chair''': '''[http://www.aes.org/ AES] standardization committee chair''' * '''Mark Yonge, AESSC Secretary''': '''[http://www.aes.org/ AES] standardization committee secretary''' * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 8e0a6c1f29027af4fe7022c753bd9a24a9c4a178 136 135 2013-05-23T14:48:49Z Noisternig 5 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): [http://www.aes.org/ AES] standardization * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 76d238a4eac43297714ec20f11ac76894838b321 139 136 2013-05-24T13:02:09Z Petibub 4 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support. == Acknowledgments == * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): [http://www.aes.org/ AES] standardization * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. eea66a519d1e5ab0c53000b18829484cffd23517 145 139 2013-05-24T15:56:46Z Petibub 4 contact to X212 added wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. Also you are invited to contact the standardization committee of X212. Join us at ([http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 93b90df1a60e4d70c0106c1f0d3fbc44007157b8 0 9 113 65 2013-05-21T12:07:09Z Isfmiho 3 wikitext text/x-wiki [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) d60afd6a797134a91db130e09d038280d8a4c5bc 114 113 2013-05-21T12:07:37Z Isfmiho 3 wikitext text/x-wiki [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 9c451bff6f0206ddc9f732ee357d48f869d68cc8 115 114 2013-05-21T12:10:13Z Isfmiho 3 wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the ARI, LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. ==Parameters== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) e564b559807905b4dbf2cc2491c8b1b5d1701933 119 115 2013-05-21T12:20:21Z Isfmiho 3 wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “din9300”. ==Parameters== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 4c1c507caa3ffbf070894add9d67f7e6223b57ea 120 119 2013-05-21T12:22:29Z Isfmiho 3 wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is “[http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]”. ==Parameters== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 0fa5956ddfa4a2aadf9b27fbd1205728c0c9e980 121 120 2013-05-21T12:22:44Z Isfmiho 3 wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. ==Parameters== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) aae2b436a1aa73a60e0abd48e060e35d8bbe3b90 0 1 116 77 2013-05-21T12:13:13Z Ente 1 Protected "[[SOFA (Spatially Oriented Format for Acoustics)]]" (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite)) wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room impulse responses (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] 0c5480a73f0781b3c3bafc7c255819f49e955afc 125 116 2013-05-22T06:56:12Z Isfmiho 3 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] aa4e771e059c0dc6e1be0a14ff6833685e74a5d3 138 125 2013-05-24T09:13:35Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. 08d7480672cd903aedf0432ee9b93c558aa00358 0 10 117 75 2013-05-21T12:13:41Z Ente 1 Protected "[[General information on SOFA]]" (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite)) wikitext text/x-wiki == General == [http://en.wikipedia.org/wiki/Head-related_transfer_function Head-related transfer functions (HRTFs)] describe the spatial filtering of the incoming sound due to the listener's anatomy. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are crucially important for the binaural reproduction of virtual acoustics. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] but also more complex data, e.g., [http://en.wikipedia.org/wiki/Impulse_response directional room impulse responses] (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were those of a [http://en.wikipedia.org/wiki/Dummy_head_recording dummy-head] microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are provided as [http://en.wikipedia.org/wiki/Impulse_response impulse responses (IRs)] with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement setups use only two microphones to record the left and right ear signals. However, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] file format should thus consider even such parameters. == Aim of SOFA == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [[netCDF-4]]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an [http://en.wikipedia.org/wiki/Impulse_response impulse response, IR]) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] corresponds to a predefined direction used in the measurements. While the representation of [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] matrix and additional matrices describing the direction of the corresponding [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF], thus, allowing to represent [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from any direction. In that formats, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from each listener are stored in a separate file. In the database storing the [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] , allowing to store [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 483c3209105db7ec907b0c96c150140c5dc8f190 124 117 2013-05-22T06:54:28Z Isfmiho 3 wikitext text/x-wiki == General == [http://en.wikipedia.org/wiki/Head-related_transfer_function Head-related transfer functions (HRTFs)] describe the spatial filtering of the incoming sound due to the listener's anatomy. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are crucially important for the binaural reproduction of virtual acoustics. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] but also more complex data, e.g., [http://en.wikipedia.org/wiki/Impulse_response directional room impulse responses] (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were those of a [http://en.wikipedia.org/wiki/Dummy_head_recording dummy-head] microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are provided as [http://en.wikipedia.org/wiki/Impulse_response impulse responses (IRs)] with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement setups use only two microphones to record the left and right ear signals. However, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] file format should thus consider even such parameters. == Aim of SOFA == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an [http://en.wikipedia.org/wiki/Impulse_response impulse response, IR]) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] corresponds to a predefined direction used in the measurements. While the representation of [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] matrix and additional matrices describing the direction of the corresponding [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF], thus, allowing to represent [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from any direction. In that formats, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from each listener are stored in a separate file. In the database storing the [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] , allowing to store [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 35e123240419dc3dddb5f29a0bd3c9a4a1fa2578 0 14 123 37 2013-05-22T06:53:08Z Isfmiho 3 wikitext text/x-wiki == Common Data Form Language (CDL) == SOFA conventions can be implemented without any programming by using CDL as suggested for [http://en.wikipedia.org/wiki/NetCDF netCDF]. CDL files allow for a [http://en.wikipedia.org/wiki/Cross-platform platform-independent] interpretation of specifications and can be compiled to a binary [http://en.wikipedia.org/wiki/NetCDF netCDF] file using the ncgen tool from the netCDF package: ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl The binaries of the nc-tools are available at the Unidata. == HDF5View == SOFA files can be loaded and edited in the [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] - a viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files. Note that SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4], which is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. d70f342c20a41042c009fbc933751eb5db8f8ca6 140 123 2013-05-24T13:13:15Z Testente 7 wikitext text/x-wiki Test == Common Data Form Language (CDL) == SOFA conventions can be implemented without any programming by using CDL as suggested for [http://en.wikipedia.org/wiki/NetCDF netCDF]. CDL files allow for a [http://en.wikipedia.org/wiki/Cross-platform platform-independent] interpretation of specifications and can be compiled to a binary [http://en.wikipedia.org/wiki/NetCDF netCDF] file using the ncgen tool from the netCDF package: ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl The binaries of the nc-tools are available at the Unidata. == HDF5View == SOFA files can be loaded and edited in the [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] - a viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files. Note that SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4], which is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. 777ba852af475567bafaf043f5d53dc4425b7133 141 140 2013-05-24T13:13:25Z Testente 7 wikitext text/x-wiki == Common Data Form Language (CDL) == SOFA conventions can be implemented without any programming by using CDL as suggested for [http://en.wikipedia.org/wiki/NetCDF netCDF]. CDL files allow for a [http://en.wikipedia.org/wiki/Cross-platform platform-independent] interpretation of specifications and can be compiled to a binary [http://en.wikipedia.org/wiki/NetCDF netCDF] file using the ncgen tool from the netCDF package: ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl The binaries of the nc-tools are available at the Unidata. == HDF5View == SOFA files can be loaded and edited in the [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] - a viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files. Note that SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4], which is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. ac46afdb4cc29c564c773b9ddb9493e3e0299313 0 18 127 92 2013-05-23T07:55:13Z Petibub 4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||time|||| || |- |N_Units||samples|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Unitsmeter|||||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.FIR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == 428c7bf775ee6882e54c269eea2693c6035287d5 129 127 2013-05-23T13:31:00Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||time|||| || |- |N_Units||samples|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Unitsmeter|||||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == f4f5a43977b6a8a418bb5f85905044c75f11e31a 130 129 2013-05-23T13:31:45Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||time|||| || |- |N_Units||samples|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == be573f62817fd6dadbb6de5c526dcdff97f5cf1e 137 130 2013-05-23T15:49:12Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling period|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == 7d17c3a180a78969f8aaaaf1e6fdb247ecb99434 142 137 2013-05-24T15:32:16Z Petibub 4 /* Fix mandatory metadata */ : added attributes title, source, and references wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling period|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == 2ba3c8405b72de9ec4414a394a6f2edf784405ab 146 142 2013-05-24T16:03:32Z Petibub 4 /* Fix versioning of SOFA and conventions */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling period|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == 2ae38ebd472b67937b27ae9fd992d7e96212a2de 147 146 2013-05-24T16:26:16Z Petibub 4 IIRBiquad added wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling period|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |G|| 1 ||MR|| broadband linear gain |- |B1|| || MRN || nominator coefficient B1 |- |B2|| || MRN || nominator coefficient B2 |- |A1|| || MRN || denominator coefficient A1 |- |A2|| || MRN || denominator coefficient A2 |- |Delay|| 0 || MR || broadband delay |- |SamplingRate|| 48000 || I || Sampling rate of the filter coefficients |- |SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == 6917b581ea0cbd3b52a8c78cc998f2a19052044e 148 147 2013-05-24T16:26:41Z Petibub 4 /* New datatype: IIRBiquad */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling period|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |G|| 1 ||MR|| broadband linear gain |- |B1|| || MRN || nominator coefficient B1 |- |B2|| || MRN || nominator coefficient B2 |- |A1|| || MRN || denominator coefficient A1 |- |A2|| || MRN || denominator coefficient A2 |- |Delay|| 0 || MR || broadband delay |- |SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == 5406a2e7132c7c2703db49a8f3ac622a8bf86f47 149 148 2013-05-24T16:33:34Z Petibub 4 /* New datatype: ComplexSpectrum */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||number of receivers||r|||| |- |E||1||||E|| |- |E_LongName||number of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling period|||| || |- |M|| - ||||M|| |- |M_LongName||number of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |G|| 1 ||MR|| broadband linear gain |- |B1|| || MRN || nominator coefficient B1 |- |B2|| || MRN || nominator coefficient B2 |- |A1|| || MRN || denominator coefficient A1 |- |A2|| || MRN || denominator coefficient A2 |- |Delay|| 0 || MR || broadband delay |- |SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Real|| ||MRN|| double || real part of the complex spectrum |- |Imag|| || MRN || double || imaginary part of the complex spectrum |} N is mandatory and must provide the frequency values. 93cc9b69a5ce9597173506784cc48ca28bd9ef2b 150 149 2013-05-24T16:37:32Z Petibub 4 /* Fix mandatory metadata */ dimensional variables optional wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||index of receivers||r|||| |- |E||1||||E|| |- |E_LongName||index of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling tap|||| || |- |M|| - ||||M|| |- |M_LongName||index of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |} == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |G|| 1 ||MR|| broadband linear gain |- |B1|| || MRN || nominator coefficient B1 |- |B2|| || MRN || nominator coefficient B2 |- |A1|| || MRN || denominator coefficient A1 |- |A2|| || MRN || denominator coefficient A2 |- |Delay|| 0 || MR || broadband delay |- |SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Real|| ||MRN|| double || real part of the complex spectrum |- |Imag|| || MRN || double || imaginary part of the complex spectrum |} N is mandatory and must provide the frequency values. 546ddc9de635d45eda83fbc5593334133f24a137 151 150 2013-05-24T16:38:28Z Petibub 4 /* New datatype: ComplexSpectrum */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||index of receivers||r|||| |- |E||1||||E|| |- |E_LongName||index of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling tap|||| || |- |M|| - ||||M|| |- |M_LongName||index of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |} == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |G|| 1 ||MR|| broadband linear gain |- |B1|| || MRN || nominator coefficient B1 |- |B2|| || MRN || nominator coefficient B2 |- |A1|| || MRN || denominator coefficient A1 |- |A2|| || MRN || denominator coefficient A2 |- |Delay|| 0 || MR || broadband delay |- |SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Real|| ||MRN|| double || real part of the complex spectrum |- |Imag|| || MRN || double || imaginary part of the complex spectrum |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. 0d1b61e5d099fd03748d3b028619ab9d5feeef00 1 20 128 93 2013-05-23T07:58:05Z Petibub 4 /* Datatype: Complex spectra */ wikitext text/x-wiki == Fix mandatory metadata == The table is in the main page. I used the following rules: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions In other words, my suggestion represents the minimal version of any conventions. Let's see if this is consistent... == Fix versioning of SOFA and conventions == For the moment, we have a version number for the SOFA specs and each conventions has its own version number. This appears rather much, but gives us more freedom (formulate that!) == Fix if datatypes can change within conventions == When we say "conventions" do we mean a fixed data type? * yes: because it will be very easy for applications: they just have to check the conventions and the data type is fixed. On the other hand, we'll need a separate conventions for each datatype even though the measurement setup might have not changed. * no: we will have conventions which do not consider the datatype (=less conventions). On the other hand, each application has either to provide '''all''' datatypes or to check two things: conventions '''and''' datatype == Datatype: Complex spectra == A new datatype has been requested, allowing to store complex spectra. While in general quite clear what to do, a few details require clarification: * Do data exist? Most of the data are saved as IRs and can be easily transformed to frequency domain on loading by the application. Data natively stored as spectra or special needs for storing data directly as spectra would help. * Most of the measured IRs are real-valued. Complex spectra introduce redundancy for those IRs, resulting in increase of the file size. This disadvantage might be small because of the compression available in SOFA. Another way to handle that would be to store only parts of the spectra. This issue should be clarified. * It seems like saving data for (sparse) discrete frequencies as complex spectra might be interesting for HRTFs coming directly from BEM simulations. New conventions and its needs in general SOFA specs are being discussed == Coordinate systems == Need to fix a few details: * In "spherical": Elevation angle vs. Zenith angle * Quaternions? 818ab1c15ecedd0eb3f95dabf7e4b4db2cd8a9f9 0 15 143 46 2013-05-24T15:49:08Z Petibub 4 wikitext text/x-wiki Currently, the following APIs are available: * API for Matlab and Octave: https://sourceforge.net/projects/sofacoustics/ == Contact == If you have questions about the SOFA API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. fb5d8176197bccdd77e9f3ca831ba73de5d2a2fd 144 143 2013-05-24T15:50:26Z Petibub 4 wikitext text/x-wiki Currently, the SOFA [https://sourceforge.net/projects/sofacoustics/ API for Matlab and Octave] is available. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. ebe2facce4713a9300276647a4ab8ab4cb99f223 0 18 152 151 2013-05-24T16:40:04Z Petibub 4 /* New datatype: ComplexSpectrum */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||index of receivers||r|||| |- |E||1||||E|| |- |E_LongName||index of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling tap|||| || |- |M|| - ||||M|| |- |M_LongName||index of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |} == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |G|| 1 ||MR|| broadband linear gain |- |B1|| || MRN || nominator coefficient B1 |- |B2|| || MRN || nominator coefficient B2 |- |A1|| || MRN || denominator coefficient A1 |- |A2|| || MRN || denominator coefficient A2 |- |Delay|| 0 || MR || broadband delay |- |SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. 02615d6de3c50335b31a81fd79969b30f1d0ba1f 153 152 2013-05-24T16:51:14Z Petibub 4 update of FIR created wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||index of receivers||r|||| |- |E||1||||E|| |- |E_LongName||index of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling tap|||| || |- |M|| - ||||M|| |- |M_LongName||index of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |} == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||MRN|| double || impulse responses |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. bc478b8e72a6e3da8609ced4390967353f88fbf3 154 153 2013-05-24T16:52:04Z Petibub 4 /* Update of datatype FIR */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||index of receivers||r|||| |- |E||1||||E|| |- |E_LongName||index of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling tap|||| || |- |M|| - ||||M|| |- |M_LongName||index of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |} == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||MRN|| double || impulse responses |- |Data.Delay|| 0 || MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. 942f0cec997376862e2cf17da8b1f8fbf00b718c 155 154 2013-05-24T16:53:16Z Petibub 4 /* Update of datatype FIR */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||r|| || |- |GLOBAL_Version||*||r|||| Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| |- |GLOBAL_SOFAConventionsVersion||*||||||Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || ||Insert the API Name here |- |GLOBAL_APIVersion||*|| || ||Insert the API Version here |- |GLOBAL_AuthorContact|||| |||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| |- |GLOBAL_Organization|||| |||| |- |GLOBAL_RoomType||free field|| |||| |- |GLOBAL_DataType||FIR|| |||| |- |GLOBAL_History|||||||| |- |GLOBAL_Source|||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*|| |||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| ||||will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| |- |ListenerPosition_Type||cartesian|||| || |- |ListenerPosition_Units||meter|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| |- |ReceiverPosition_Type||cartesian|||||| |- |ReceiverPosition_Units||meter|| |||| |- |SourcePosition||[0 0 0]||||IC, MC|| |- |SourcePosition_Type||cartesian|||||| |- |SourcePosition_Units||meter|| |||| |- |EmitterPosition||[0 0 0]||||eCI, eCM|| |- |EmitterPosition_Type||cartesian|||||| |- |EmitterPosition_Units||meter|||||| |- |Data.IR||[1 1]||||mRn||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||index of receivers||r|||| |- |E||1||||E|| |- |E_LongName||index of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling tap|||| || |- |M|| - ||||M|| |- |M_LongName||index of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |} == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||MRN|| double || impulse responses |- |Data.Delay|| 0 || MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} d2a3225f556cb4d57f67be5e0d63bfa856d57da4 156 155 2013-05-24T17:02:45Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version||*||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| || |- |GLOBAL_SOFAConventionsVersion||*|||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || |||| Insert the API Name here |- |GLOBAL_APIVersion||*|| || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated||*|| |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |- |Data.IR||[1 1]||||mRn||double ||Only mandatory when DataType is FIR |- |Data.Delay||0||||MR||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. {| border="1" !Name !Default !Read-Only !Dimensions !Comment |- |I||1||r||I|| |- |I_LongName||singleton dimension||r|| || |- |R||2||||R|| |- |R_LongName||index of receivers||r|||| |- |E||1||||E|| |- |E_LongName||index of emitters||r|||| |- |N|| - ||||N|| |- |N_LongName||index|||| || |- |N_Units||sampling tap|||| || |- |M|| - ||||M|| |- |M_LongName||index of measurements||r |||| |- |C||3||r||C|| |- |C_LongName||coordinate triplet||r|||| |} == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||MRN|| double || impulse responses |- |Data.Delay|| 0 || MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 6ea8a7420015c55830fc3cdeaf1e9aa32af45699 157 156 2013-05-24T17:05:13Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version||*||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| || |- |GLOBAL_SOFAConventionsVersion||*|||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || |||| Insert the API Name here |- |GLOBAL_APIVersion||*|| || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated||*|| |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |- |Data.IR||[1 1]||||mRn||double ||Only mandatory when DataType is FIR |- |Data.Delay||0||||MR||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||MRN|| double || impulse responses |- |Data.Delay|| 0 || MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} d81fdcb6b7e2afe3a156e3a4e3690ba63b75ee7f 159 157 2013-05-27T13:02:22Z Petibub 4 /* Update of datatype FIR */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version||*||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| || |- |GLOBAL_SOFAConventionsVersion||*|||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || |||| Insert the API Name here |- |GLOBAL_APIVersion||*|| || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated||*|| |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |- |Data.IR||[1 1]||||mRn||double ||Only mandatory when DataType is FIR |- |Data.Delay||0||||MR||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||MRN|| double || impulse responses |- |Data.Delay|| 0 || MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 039a16a88c2aab102136a563daf666dd11ff1982 160 159 2013-05-27T13:03:49Z Petibub 4 /* Update of datatype FIR */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version||*||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| || |- |GLOBAL_SOFAConventionsVersion||*|||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || |||| Insert the API Name here |- |GLOBAL_APIVersion||*|| || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated||*|| |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |- |Data.IR||[1 1]||||mRn||double ||Only mandatory when DataType is FIR |- |Data.Delay||0||||MR||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||MRN|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} c156c56c53e79f13a9345a50fbdeb8ed72b9575a 161 160 2013-05-27T13:06:38Z Petibub 4 /* Update of datatype FIR */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version||*||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| || |- |GLOBAL_SOFAConventionsVersion||*|||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || |||| Insert the API Name here |- |GLOBAL_APIVersion||*|| || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated||*|| |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |- |Data.IR||[1 1]||||mRn||double ||Only mandatory when DataType is FIR |- |Data.Delay||0||||MR||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||MRN|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 60d6d4b480595f0bd25a3003212f7cd0e087d63a 162 161 2013-05-27T13:06:53Z Petibub 4 /* New datatype: ComplexSpectrum */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version||*||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| || |- |GLOBAL_SOFAConventionsVersion||*|||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || |||| Insert the API Name here |- |GLOBAL_APIVersion||*|| || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated||*|| |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |- |Data.IR||[1 1]||||mRn||double ||Only mandatory when DataType is FIR |- |Data.Delay||0||||MR||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 2802cb896819630e9347736e7b510b3dafa5d507 163 162 2013-05-27T13:08:40Z Petibub 4 /* Update of datatype FIR */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version||*||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| || |- |GLOBAL_SOFAConventionsVersion||*|||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || |||| Insert the API Name here |- |GLOBAL_APIVersion||*|| || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated||*|| |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |- |Data.IR||[1 1]||||mRn||double ||Only mandatory when DataType is FIR |- |Data.Delay||0||||MR||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| || MRN || double || imaginary part of the complex spectrum |- |N|| || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} eb3256f55521a89dae97626218b14d039e43f6c6 164 163 2013-05-27T13:09:03Z Petibub 4 /* New datatype: ComplexSpectrum */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version||*||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR|| |||| || |- |GLOBAL_SOFAConventionsVersion||*|||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName||*|| || |||| Insert the API Name here |- |GLOBAL_APIVersion||*|| || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated||*|| |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*|| |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |- |Data.IR||[1 1]||||mRn||double ||Only mandatory when DataType is FIR |- |Data.Delay||0||||MR||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate||48000||||I||double ||Only mandatory when DataType is FIR |- |Data.SamplingRate_Units||hertz|| || || || Only mandatory when DataType is FIR |} Note: we consider the Data as mandatory, thus, if DataType is default (=FIR) then Data.FIR, Data.SamplingRate, and Data.SamplingRate_Units must be provided. Otherwise, the correct Data-fields must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} ec123b5543450684358607afb10a24690a68f228 165 164 2013-05-27T13:22:31Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Fix versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 324a487384e383d8b23737420af72696d28c895c 173 165 2013-05-27T19:45:49Z 91.119.127.146 0 /* Fix versioning of SOFA and conventions */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Fix if datatypes can change within conventions == == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 85d9558d8c1d0d4038bdb62c0276eb7f42a1b92d 174 173 2013-05-27T19:47:39Z 91.119.127.146 0 /* Fix if datatypes can change within conventions */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems == == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 7780614fe9f5b6224972e1a776f9c94ae3e80f5d 175 174 2013-05-27T19:48:57Z 91.119.127.146 0 /* Fix the coordinate systems */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Fix the naming of the units == == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} e6d3f2834c14f1ffb614e8a0d943ac341711b7b9 176 175 2013-05-27T19:49:24Z 91.119.127.146 0 /* Fix the naming of the units */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Naming of the units == lowercase, the rest is not clarified yet. == Include strings as variables == == Clarify the role of dimension variables == == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} b9473d010e812c66f8c21d65881eb7ce27e52987 178 176 2013-05-27T19:54:25Z Petibub 4 /* Clarify the role of dimension variables */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_DatabaseTimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Naming of the units == lowercase, the rest is not clarified yet. == Include strings as variables == == Role of dimension variables == At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 9d5032d6cffeed053a18a2f73f018ea8e769ac43 179 178 2013-05-28T09:43:34Z 193.171.195.57 0 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Fix mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Naming of the units == lowercase, the rest is not clarified yet. == Include strings as variables == == Role of dimension variables == At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 2d65eb35bd7d08968bdbc5e22781de1e502cf7e6 180 179 2013-05-28T15:20:30Z 193.171.195.57 0 /* Fix mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Naming of the units == lowercase, the rest is not clarified yet. == Include strings as variables == == Role of dimension variables == At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} 386e8140348652287cb0f4d869d813f5a101d997 181 180 2013-05-28T15:21:52Z Petibub 4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Naming of the units == lowercase, the rest is not clarified yet. == Include strings as variables == == Role of dimension variables == At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == 930b39c935578199c366ca41489ad2ecd7de1656 182 181 2013-05-28T15:37:18Z Petibub 4 /* RoomType */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Naming of the units == lowercase, the rest is not clarified yet. == Include strings as variables == == Role of dimension variables == At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == New datatype: IIRBiquad == {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} == New datatype: ComplexSpectrum == {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. == Update of datatype FIR == The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. 59791646094e54ef708489e1ed9f6bfb9e4ee9ea 183 182 2013-05-28T15:38:29Z Petibub 4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Naming of the units == lowercase, the rest is not clarified yet. == Include strings as variables == == Role of dimension variables == At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == Datatypes == === New: IIRBiquad === {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} === New: ComplexSpectrum === {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. === Update: FIR === The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. 812b97f094aee60cd9fc05d566895cf988b8deff 184 183 2013-05-28T15:38:46Z Petibub 4 /* Datatypes */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Versioning of SOFA and conventions == Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. == Can datatypes change within conventions? == If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. == Fix the coordinate systems within conventions? == Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. == Naming of the units == lowercase, the rest is not clarified yet. == Include strings as variables == == Role of dimension variables == At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == DataType == === New: IIRBiquad === {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} === New: ComplexSpectrum === {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. === Update: FIR === The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. 84398f302cf9601237ef0438ee7fbe440dc4559b 188 184 2013-05-28T16:01:21Z Petibub 4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == The metadata mandatory in all SOFA conventions have not been fixed yet. We propose to have the following metadata mandatory in all SOFA conventions: {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Various issues == === Versioning of SOFA and conventions === Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. === Can datatypes change within conventions? === If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. === Fix the coordinate systems within conventions? === Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. === Naming of the units === lowercase, the rest is not clarified yet. === Include strings as variables === === Role of dimension variables === At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == DataType == === New: IIRBiquad === {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} === New: ComplexSpectrum === {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. === Update: FIR === The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. 352bee21690bfce4d62e1ec3abe90f078049dc5a 190 188 2013-05-28T16:03:10Z Petibub 4 /* Mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == We propose the following metadata to be mandatory for '''all''' SOFA conventions. Following rules must be fulfilled: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Various issues == === Versioning of SOFA and conventions === Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. === Can datatypes change within conventions? === If yes, any application would have either to implement all possible datatypes or to check if the supported datatype is given within the conventions. Thus, no, until we will have so many conventions with only the datatype changing that we decide to change this decision. === Fix the coordinate systems within conventions? === Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. === Naming of the units === lowercase, the rest is not clarified yet. === Include strings as variables === === Role of dimension variables === At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == DataType == === New: IIRBiquad === {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} === New: ComplexSpectrum === {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. === Update: FIR === The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. 2e02b448d9f0a386d2504a553ee63f8d4736bc40 193 190 2013-05-28T16:10:49Z Petibub 4 /* Can datatypes change within conventions? */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == We propose the following metadata to be mandatory for '''all''' SOFA conventions. Following rules must be fulfilled: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Various issues == === Versioning of SOFA and conventions === Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. === Allow various DataTypes within a single SOFAConventions? === * Fixed DataType: ** Pro: very simple for applications: they just have to check the conventions and the data type is known. ** Con: separate conventions for each DataType required even though the measurement setup might have not changed. * Arbitrary DataType allowed: ** Pro: less conventions, we will have conventions which do not consider the datatype. ** Con: Each application has either to provide '''all''' datatypes and branch while processing between the different algorithms, or to check both Conventions '''and''' DataType on loading. At the moment we have 1 stable and 2 proposed SOFA Conventions. This number is rather low, thus we wait until we'll have more conventions and then decide if we want to allow to separate DataType from SOFAConventions. === Fix the coordinate systems within conventions? === Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. === Naming of the units === lowercase, the rest is not clarified yet. === Include strings as variables === === Role of dimension variables === At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == DataType == === New: IIRBiquad === {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} === New: ComplexSpectrum === {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. === Update: FIR === The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. 72fe01108a1b109ddb00b9078ba3e97e78e1d695 1 19 158 122 2013-05-24T17:17:25Z Petibub 4 /* Include calibration data */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == Measured data exist as IRs. More information on metadata and measurement setups required. Corresponding researchers contacted. Waiting for response... == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". * Seems like we need a good definition of "raw", "processed", and "un-calibrated". Then we could provide an attribute, e.g., ProcessingState. Otherwise, we could use "ProcessingState" in the same way we use "Comments", namely, include a narrative description of the processing steps. Then we could write GLOBAL_ProcessingState = "Deconvolution with exp. sweep, windowing at ..., filtering at..." and so on. Applications which do not care, could ignore it; researchers who care could interpret it. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. * It seems like we would need to save the IRs from speaker(s) and microphone(s) together with other metadata like levels. Would it be sufficient to store that information in a separate SOFA file? Applications which do not care, would not have this ballast. Researchers who care, could use it to reproduce all post-processing steps. A new SOFA conventions for calibration would do - Does it make sense? * Seems like level would be important. Intermediate results: specifications for the level required, name for the variable required? Then, we could have level as an optional variable in SOFA. Also, some data would be nice == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 0b8da298067971ec07adfd85ec5b840f06e272c9 195 158 2013-05-30T10:36:03Z 147.162.231.98 0 /* Headphone transfer functions (HpTFs) */ wikitext text/x-wiki == Headphone transfer functions (HpTFs) == No public HpIR databases nor standard HpIR repositories have been proposed to date. Typically, small sets of headphones are tested limited to the purpose of reproducing a virtual auditory scene (VAS) for a specific experiment and subject. Recent auralization softwares cluster headphones by type ( i.e. earphones, in-ear headphones, closed-back or open-back circumaural), each capturing common behaviours for a generic listener. However, given H headphone models and L listeners it is possible to measure H x L individual HpIRs. Analyses of headphone-to-external ear transfer functions, ear canal entrance-to-eardrum transfer functions and impedance mismatch need to be carried on in order to understand and control sound artifacts introduced by headphones. These responses need to be methodically stored in specific data structures sharing common features with individual HRIR databases. The key observations that guide the design of such discussed convention are: * HpIRs are highly sensitive to the positioning of headphones; * both closed- and open-ear canal measurements are required for the evaluation of binaural reproduction; * how the headphones interact with the external ear is strictly subject-dependent. As a matter of fact, the intersubjective variation is particularly marked in the high-frequency range, where important elevation cues generally lie. Thus, an inaccurate compensation likely leads to spectral colorations that affect both source elevation perception and sound externalization Indeed, one of the purposes of HpIRs recordings is to compute the equalization filter that compensates the headphone starting from the raw HpIRs. For each pair of headphones, a collection of individual HpIRs and equalization filters are stored with respect to a specific subject. It is desirable to have a ''foreign key'' to the HRIRs set recorded on the same subject in order to provide data for an individual binaural listening experience. For every subject, three data containers - raw, compensated and eq - could be defined. * the raw data from the recordings * the compensated impulse responses * the equalization filter (under the form of an impulse response) obtained from the inverse HpIR through one or more techniques, e.g. considering the mean HpIR measurement with respect to all the repositionaments of that device. The following information: * headphone model, producer included (''following a similar approach used for anthropometric data (AD)''); specific characteristics of the headphones such as transducer type, acoustic coupling, and design are stored in their data sheet. * eq algorithm, equalization algorithm used The storage of individual headphone compensation filters promotes the personal use of headphones. This is especially true in experimental environments, yet HpIR modeling and cluster analysis would allow the extension of this approach to a commercial domain. == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". * Seems like we need a good definition of "raw", "processed", and "un-calibrated". Then we could provide an attribute, e.g., ProcessingState. Otherwise, we could use "ProcessingState" in the same way we use "Comments", namely, include a narrative description of the processing steps. Then we could write GLOBAL_ProcessingState = "Deconvolution with exp. sweep, windowing at ..., filtering at..." and so on. Applications which do not care, could ignore it; researchers who care could interpret it. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. * It seems like we would need to save the IRs from speaker(s) and microphone(s) together with other metadata like levels. Would it be sufficient to store that information in a separate SOFA file? Applications which do not care, would not have this ballast. Researchers who care, could use it to reproduce all post-processing steps. A new SOFA conventions for calibration would do - Does it make sense? * Seems like level would be important. Intermediate results: specifications for the level required, name for the variable required? Then, we could have level as an optional variable in SOFA. Also, some data would be nice == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 6befaa01c300b28c55c24ea58a36d4520b69cfbc 0 5 166 85 2013-05-27T13:43:34Z Petibub 4 SimpleFreeFieldHRIR and SimpleFreeFieldTF added wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldHRIR]]: adaptation of the previous version of SimpleFreeFieldHRIR for SOFA 0.4 * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses ComplexSpectrum as DataType covering special needs coming from HRTF simulations * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Headphone transfer functions: data exist, need more information on metadata * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! a22afcb62adcfbd8ace78d867ac402727440d624 187 166 2013-05-28T15:59:27Z Petibub 4 /* Proposed SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldHRIR]]: adaptation of the previous version of SimpleFreeFieldHRIR for SOFA 0.4 * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses ComplexSpectrum as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Headphone transfer functions: data exist, need more information on metadata * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 542bcd53b0a1f9693f99bd02075bd00577a40ee4 0 9 167 121 2013-05-27T13:45:19Z Petibub 4 Added proposed for SOFA 0.4 wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (used in SOFA 0.3)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 8abf52b429e8bc67839c1c500c9bf3d8a9556372 168 167 2013-05-27T13:47:16Z Petibub 4 /* Proposed (for SOFA 0.4) */ wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |---- |GLOBAL_Conventions |SOFA |rm | | | |---- |GLOBAL_Version |0.3 |rm | | | |---- |GLOBAL_SOFAConventions |SimpleFreeFieldHRIR |rm | | | |---- |GLOBAL_SOFAConventionsVersion |0.1 |m | | | |---- |GLOBAL_APIName | |rm | | |Insert the API Name here |---- |GLOBAL_APIVersion | |rm | | |Insert the API Version here |---- |GLOBAL_ApplicationName | |m | | | |---- |GLOBAL_ApplicationVersion | |m | | | |---- |GLOBAL_AuthorContact | |m | | | |---- |GLOBAL_License |No license provided, ask the author for permission |m | | | |---- |GLOBAL_Organization | |m | | | |---- |GLOBAL_DatabaseName | |m | | | |---- |GLOBAL_SubjectID | |m | | | |---- |GLOBAL_RoomType |free field |m | | | |---- |GLOBAL_DataType |FIR |m | | | |---- |GLOBAL_History | | | | | |---- |GLOBAL_Comment | | | | | |---- |GLOBAL_DatabaseTimeCreated | |m | | |will be updated when saving and not existing or empty |---- |GLOBAL_DatabaseTimeModified | |m | | |will be updated each time when saving |---- |ListenerPosition | [1 0 0] |m |IC, MC |double | |---- |ListenerPosition_Type |cartesian |m | | | |---- |ListenerPosition_Units |meter |m | | | |---- |ListenerUp |[1.2 0 1] |m |IC, MC |double | |---- |ListenerUp_Type |cartesian |m | | | |---- |ListenerUp_Units |meter |m | | | |---- |ListenerView |[0 0 0] |m |IC, MC |double | |---- |ListenerView_Type |cartesian |m | | | |---- |ListenerView_Units |meter |m | | | |---- |ListenerRotation |[0 0 0] |m |IC, MC |double | |---- |ListenerRotation_Type |din9300 |m | | | |---- |ListenerRotation_Units |degrees |m | | | |---- |ReceiverPosition |[0 -0.09 0; 0 0.09 0] |m |rCI, rCM |double | |---- |ReceiverPosition_Type |cartesian |m | | | |---- |ReceiverPosition_Units |meter |m | | | |---- |SourcePosition |[0 0 0] |m |IC, MC |double | |---- |SourcePosition_Type |cartesian |m | | | |---- |SourcePosition_Units |meter |m | | | |---- |SourceUp |[0 0 1] |m |IC, MC |double | |---- |SourceUp_Type |cartesian |m | | | |---- |SourceUp_Units |meter |m | | | |---- |SourceView |[1 0 0] |m |IC, MC |double | |---- |SourceView_Type |cartesian |m | | | |---- |SourceView_Units |meter |m | | | |---- |EmitterPosition |[0 0 0] |m |eCI, eCM |double | |---- |EmitterPosition_Type |cartesian |m | | | |---- |EmitterPosition_Units |meter |m | | | |---- |Data.IR |[1 1] |m |mRn |double | |---- |Data.SamplingRate |48000 |m |I |double | |---- |Data.SamplingRate_Units |hertz |m | | | |---- |Data.Delay |0 |m |IM, RM |double | |---- |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (used in SOFA 0.3)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 50945bf74ed1de3d63b2fec5ddd64abab0623943 170 168 2013-05-27T14:09:43Z Petibub 4 /* Proposed (for SOFA 0.4) */ wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |---- |GLOBAL_Conventions |SOFA |rm | | | |---- |GLOBAL_Version |0.3 |rm | | | |---- |GLOBAL_SOFAConventions |SimpleFreeFieldHRIR |rm | | | |---- |GLOBAL_SOFAConventionsVersion |0.1 |m | | | |---- |GLOBAL_APIName | |rm | | |Insert the API Name here |---- |GLOBAL_APIVersion | |rm | | |Insert the API Version here |---- |GLOBAL_ApplicationName | |m | | | |---- |GLOBAL_ApplicationVersion | |m | | | |---- |GLOBAL_AuthorContact | |m | | | |---- |GLOBAL_License |No license provided, ask the author for permission |m | | | |---- |GLOBAL_Organization | |m | | | |---- |GLOBAL_DatabaseName | |m | | | |---- |GLOBAL_SubjectID | |m | | | |---- |GLOBAL_RoomType |free field |m | | | |---- |GLOBAL_DataType |FIR |m | | | |---- |GLOBAL_History | | | | | |---- |GLOBAL_Comment | | | | | |---- |GLOBAL_DatabaseTimeCreated | |m | | |will be updated when saving and not existing or empty |---- |GLOBAL_DatabaseTimeModified | |m | | |will be updated each time when saving |---- |ListenerPosition | [1 0 0] |m |IC, MC |double | |---- |ListenerPosition_Type |cartesian |m | | | |---- |ListenerPosition_Units |meter |m | | | |---- |ListenerUp |[1.2 0 1] |m |IC, MC |double | |---- |ListenerUp_Type |cartesian |m | | | |---- |ListenerUp_Units |meter |m | | | |---- |ListenerView |[0 0 0] |m |IC, MC |double | |---- |ListenerView_Type |cartesian |m | | | |---- |ListenerView_Units |meter |m | | | |---- |ListenerRotation |[0 0 0] |m |IC, MC |double | |---- |ListenerRotation_Type |din9300 |m | | | |---- |ListenerRotation_Units |degrees |m | | | |---- |ReceiverPosition |[0 -0.09 0; 0 0.09 0] |m |rCI, rCM |double | |---- |ReceiverPosition_Type |cartesian |m | | | |---- |ReceiverPosition_Units |meter |m | | | |---- |SourcePosition |[0 0 0] |m |IC, MC |double | |---- |SourcePosition_Type |cartesian |m | | | |---- |SourcePosition_Units |meter |m | | | |---- |EmitterPosition |[0 0 0] |m |eCI, eCM |double | |---- |EmitterPosition_Type |cartesian |m | | | |---- |EmitterPosition_Units |meter |m | | | |---- |Data.IR |[1 1] |m |mRn |double | |---- |Data.SamplingRate |48000 |m |I |double | |---- |Data.SamplingRate_Units |hertz |m | | | |---- |Data.Delay |[0 0] |m |IR, MR |double | |---- |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (used in SOFA 0.3)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) e2808599b0cd103ffcab318145287bafc01d8d67 171 170 2013-05-27T19:30:16Z 91.119.127.146 0 /* Proposed (for SOFA 0.4) */ wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.3||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.1||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History|||||||||| |- |GLOBAL_Comment|||||||||| |- |GLOBAL_DatabaseTimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[1.2 0 1]||m||IC, MC||double|| |- |ListenerUp_Type||cartesian||m|||||| |- |ListenerUp_Units||meter||m|||||| |- |ListenerView||[0 0 0]||m||IC, MC||double|| |- |ListenerView_Type||cartesian||m|||||| |- |ListenerView_Units||meter||m|||||| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (used in SOFA 0.3)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 16bccdae63ac2a904ec456f0b3e0f01669c83577 356 171 2013-06-20T13:37:51Z Petibub 4 /* Proposed (for SOFA 0.4) */ wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done at a constant distance in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (used in SOFA 0.3)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 107cb58794a3993caff3ad6b39d8c91ff8257d25 381 356 2013-06-21T09:01:07Z Petibub 4 wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. Source: Source is in the origin of the setup and consists of a single emitter. SourcePosition: (0 0 0), SourceUp: (0 0 1), SourceView: (1 0 0), SourceRotation, and EmitterPosition: (0 0 0). * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (used in SOFA 0.3)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) c04c59bc14c03cfc486af98edd38e6a7ec494fbf 382 381 2013-06-21T09:31:40Z Petibub 4 wikitext text/x-wiki ==Description== [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. The SOFA conventions SimpleFreeFieldHRIR defines such a setup. It requires: General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... Data: The number of receivers is two, thus, the size of Data.IR is [M 2 N]. Only a single sampling rate for the file is allowed, thus SamplingRate is a scalar. * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (used in SOFA 0.3)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 6a7d177a85af5e98fe270b21acc8261d74803fcb 0 24 169 2013-05-27T14:08:10Z Petibub 4 Created page with "This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is ComplexSpectrum. This Conventions was requested to cover th..." wikitext text/x-wiki This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is ComplexSpectrum. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. ==Proposed for SOFA 0.4== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |---- |GLOBAL_Conventions |SOFA |rm | | | |---- |GLOBAL_Version |0.4 |rm | | | |---- |GLOBAL_SOFAConventions |SimpleFreeFieldTF |rm | | | |---- |GLOBAL_SOFAConventionsVersion |0.1 |m | | | |---- |GLOBAL_APIName | |rm | | |Insert the API Name here |---- |GLOBAL_APIVersion | |rm | | |Insert the API Version here |---- |GLOBAL_ApplicationName | |m | | | |---- |GLOBAL_ApplicationVersion | |m | | | |---- |GLOBAL_AuthorContact | |m | | | |---- |GLOBAL_License |No license provided, ask the author for permission |m | | | |---- |GLOBAL_Organization | |m | | | |---- |GLOBAL_DatabaseName | |m | | | |---- |GLOBAL_SubjectID | |m | | | |---- |GLOBAL_RoomType |free field |m | | | |---- |GLOBAL_DataType |ComplexSpectrum |m | | | |---- |GLOBAL_History | | | | | |---- |GLOBAL_Comment | | | | | |---- |GLOBAL_DatabaseTimeCreated | |m | | |will be updated when saving and not existing or empty |---- |GLOBAL_DatabaseTimeModified | |m | | |will be updated each time when saving |---- |ListenerPosition | [1 0 0] |m |IC, MC |double | |---- |ListenerPosition_Type |cartesian |m | | | |---- |ListenerPosition_Units |meter |m | | | |---- |ListenerUp |[1.2 0 1] |m |IC, MC |double | |---- |ListenerUp_Type |cartesian |m | | | |---- |ListenerUp_Units |meter |m | | | |---- |ListenerView |[0 0 0] |m |IC, MC |double | |---- |ListenerView_Type |cartesian |m | | | |---- |ListenerView_Units |meter |m | | | |---- |ListenerRotation |[0 0 0] |m |IC, MC |double | |---- |ListenerRotation_Type |din9300 |m | | | |---- |ListenerRotation_Units |degrees |m | | | |---- |ReceiverPosition |[0 -0.09 0; 0 0.09 0] |m |rCI, rCM |double | |---- |ReceiverPosition_Type |cartesian |m | | | |---- |ReceiverPosition_Units |meter |m | | | |---- |SourcePosition |[0 0 0] |m |IC, MC |double | |---- |SourcePosition_Type |cartesian |m | | | |---- |SourcePosition_Units |meter |m | | | |---- |SourceUp |[0 0 1] |m |IC, MC |double | |---- |SourceUp_Type |cartesian |m | | | |---- |SourceUp_Units |meter |m | | | |---- |SourceView |[1 0 0] |m |IC, MC |double | |---- |SourceView_Type |cartesian |m | | | |---- |SourceView_Units |meter |m | | | |---- |EmitterPosition |[0 0 0] |m |eCI, eCM |double | |---- |EmitterPosition_Type |cartesian |m | | | |---- |EmitterPosition_Units |meter |m | | | |---- |Data.Real |[1 1] |m |mRn |double | |---- |Data.Imag |[0 0] |m |MRN |double | |---- |N |0 |m |N |double | |---- |N_LongName |frequency | | | | |---- |N_Units |hertz | | | | |---- |} 158df23ef790e82e8fe6d65c3c2a6e246d4e7fc7 172 169 2013-05-27T19:31:04Z 91.119.127.146 0 /* Proposed for SOFA 0.4 */ wikitext text/x-wiki This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is ComplexSpectrum. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. ==Proposed for SOFA 0.4== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldTF||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.1||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||ComplexSpectrum||rm|||||| |- |GLOBAL_History|||||||||| |- |GLOBAL_Comment|||||||||| |- |GLOBAL_DatabaseTimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[1.2 0 1]||m||IC, MC||double|| |- |ListenerUp_Type||cartesian||m|||||| |- |ListenerUp_Units||meter||m|||||| |- |ListenerView||[0 0 0]||m||IC, MC||double|| |- |ListenerView_Type||cartesian||m|||||| |- |ListenerView_Units||meter||m|||||| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceUp_Type||cartesian||m|||||| |- |SourceUp_Units||meter||m|||||| |- |SourceView||[1 0 0]||m||IC, MC||double|| |- |SourceView_Type||cartesian||m|||||| |- |SourceView_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency|||||||| |- |N_Units||hertz|||||||| |} ab950330bcd4138f1f23d112fa10fdec51f77a54 357 172 2013-06-20T13:38:57Z Petibub 4 updated to SOFA 0.4 draft version wikitext text/x-wiki This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is ComplexSpectrum. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. ==Proposed for SOFA 0.4== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldTF||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.1||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency|||||||| |- |N_Units||hertz|||||||| |} eef4af06f4ce725a88474fe5bcdc6fa5fa54e463 1 20 177 128 2013-05-27T19:51:14Z 91.119.127.146 0 /* Datatype: Complex spectra */ wikitext text/x-wiki == Fix mandatory metadata == The table is in the main page. I used the following rules: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions In other words, my suggestion represents the minimal version of any conventions. Let's see if this is consistent... == Fix versioning of SOFA and conventions == For the moment, we have a version number for the SOFA specs and each conventions has its own version number. This appears rather much, but gives us more freedom (formulate that!) == Fix if datatypes can change within conventions == When we say "conventions" do we mean a fixed data type? * yes: because it will be very easy for applications: they just have to check the conventions and the data type is fixed. On the other hand, we'll need a separate conventions for each datatype even though the measurement setup might have not changed. * no: we will have conventions which do not consider the datatype (=less conventions). On the other hand, each application has either to provide '''all''' datatypes or to check two things: conventions '''and''' datatype == Datatype: Complex spectra == A new datatype has been requested, allowing to store complex spectra. While in general quite clear what to do, a few details require clarification: * Do data exist? Most of the data are saved as IRs and can be easily transformed to frequency domain on loading by the application. Data natively stored as spectra or special needs for storing data directly as spectra would help. * Most of the measured IRs are real-valued. Complex spectra introduce redundancy for those IRs, resulting in increase of the file size. This disadvantage might be small because of the compression available in SOFA. Another way to handle that would be to store only parts of the spectra. This issue should be clarified. * It seems like saving data for (sparse) discrete frequencies as complex spectra might be interesting for HRTFs coming directly from BEM simulations. New conventions and its needs in general SOFA specs are being discussed * '''Fixed''': Conventions and DataType proposed. == Coordinate systems == Need to fix a few details: * In "spherical": Elevation angle vs. Zenith angle * Quaternions? a8f9629f95c90534ce60c0d88ec83ff181a49a70 189 177 2013-05-28T16:02:10Z Petibub 4 /* Fix mandatory metadata */ wikitext text/x-wiki == Fix versioning of SOFA and conventions == For the moment, we have a version number for the SOFA specs and each conventions has its own version number. This appears rather much, but gives us more freedom (formulate that!) == Fix if datatypes can change within conventions == When we say "conventions" do we mean a fixed data type? * yes: because it will be very easy for applications: they just have to check the conventions and the data type is fixed. On the other hand, we'll need a separate conventions for each datatype even though the measurement setup might have not changed. * no: we will have conventions which do not consider the datatype (=less conventions). On the other hand, each application has either to provide '''all''' datatypes or to check two things: conventions '''and''' datatype == Datatype: Complex spectra == A new datatype has been requested, allowing to store complex spectra. While in general quite clear what to do, a few details require clarification: * Do data exist? Most of the data are saved as IRs and can be easily transformed to frequency domain on loading by the application. Data natively stored as spectra or special needs for storing data directly as spectra would help. * Most of the measured IRs are real-valued. Complex spectra introduce redundancy for those IRs, resulting in increase of the file size. This disadvantage might be small because of the compression available in SOFA. Another way to handle that would be to store only parts of the spectra. This issue should be clarified. * It seems like saving data for (sparse) discrete frequencies as complex spectra might be interesting for HRTFs coming directly from BEM simulations. New conventions and its needs in general SOFA specs are being discussed * '''Fixed''': Conventions and DataType proposed. == Coordinate systems == Need to fix a few details: * In "spherical": Elevation angle vs. Zenith angle * Quaternions? 1165895dcc12720f8aeb272e3ae47cd82371d9e1 191 189 2013-05-28T16:03:47Z Petibub 4 /* Fix versioning of SOFA and conventions */ wikitext text/x-wiki == Fix if datatypes can change within conventions == When we say "conventions" do we mean a fixed data type? * yes: because it will be very easy for applications: they just have to check the conventions and the data type is fixed. On the other hand, we'll need a separate conventions for each datatype even though the measurement setup might have not changed. * no: we will have conventions which do not consider the datatype (=less conventions). On the other hand, each application has either to provide '''all''' datatypes or to check two things: conventions '''and''' datatype == Datatype: Complex spectra == A new datatype has been requested, allowing to store complex spectra. While in general quite clear what to do, a few details require clarification: * Do data exist? Most of the data are saved as IRs and can be easily transformed to frequency domain on loading by the application. Data natively stored as spectra or special needs for storing data directly as spectra would help. * Most of the measured IRs are real-valued. Complex spectra introduce redundancy for those IRs, resulting in increase of the file size. This disadvantage might be small because of the compression available in SOFA. Another way to handle that would be to store only parts of the spectra. This issue should be clarified. * It seems like saving data for (sparse) discrete frequencies as complex spectra might be interesting for HRTFs coming directly from BEM simulations. New conventions and its needs in general SOFA specs are being discussed * '''Fixed''': Conventions and DataType proposed. == Coordinate systems == Need to fix a few details: * In "spherical": Elevation angle vs. Zenith angle * Quaternions? 6382516af6f0ac0bf6ac9837aa9607e3eb649881 192 191 2013-05-28T16:04:20Z Petibub 4 /* Fix if datatypes can change within conventions */ wikitext text/x-wiki == Datatype: Complex spectra == A new datatype has been requested, allowing to store complex spectra. While in general quite clear what to do, a few details require clarification: * Do data exist? Most of the data are saved as IRs and can be easily transformed to frequency domain on loading by the application. Data natively stored as spectra or special needs for storing data directly as spectra would help. * Most of the measured IRs are real-valued. Complex spectra introduce redundancy for those IRs, resulting in increase of the file size. This disadvantage might be small because of the compression available in SOFA. Another way to handle that would be to store only parts of the spectra. This issue should be clarified. * It seems like saving data for (sparse) discrete frequencies as complex spectra might be interesting for HRTFs coming directly from BEM simulations. New conventions and its needs in general SOFA specs are being discussed * '''Fixed''': Conventions and DataType proposed. == Coordinate systems == Need to fix a few details: * In "spherical": Elevation angle vs. Zenith angle * Quaternions? 5b6d15239e83598cbb29c007b5288f1b2e6d3ea0 194 192 2013-05-28T16:11:47Z Petibub 4 /* Datatype: Complex spectra */ wikitext text/x-wiki == Datatype: Complex spectra == '''Fixed''': Conventions and DataType proposed. Discussion A new datatype has been requested, allowing to store complex spectra. While in general quite clear what to do, a few details require clarification: * Do data exist? Most of the data are saved as IRs and can be easily transformed to frequency domain on loading by the application. Data natively stored as spectra or special needs for storing data directly as spectra would help. * Most of the measured IRs are real-valued. Complex spectra introduce redundancy for those IRs, resulting in increase of the file size. This disadvantage might be small because of the compression available in SOFA. Another way to handle that would be to store only parts of the spectra. This issue should be clarified. * It seems like saving data for (sparse) discrete frequencies as complex spectra might be interesting for HRTFs coming directly from BEM simulations. New conventions and its needs in general SOFA specs are being discussed == Coordinate systems == Need to fix a few details: * In "spherical": Elevation angle vs. Zenith angle * Quaternions? d6211f46e5b81cb69a9765c6323ea7741ddfa7e0 0 25 185 2013-05-28T15:57:09Z Petibub 4 Created page with "==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This conventions defines a setup used for measuring DRIRs in a single room with a single excitation source and a..." wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This conventions defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SingleRoomDRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.0||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||reverberant||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[1 0 1]||m||IC, MC||double|| |- |ListenerUp_Type||cartesian||m|||||| |- |ListenerUp_Units||meter||m|||||| |- |ListenerView||[0 0 0]||m||IC, MC||double|| |- |ListenerView_Type||cartesian||m|||||| |- |ListenerView_Units||meter||m|||||| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceUp_Type||cartesian||m|||||| |- |SourceUp_Units||meter||m|||||| |- |SourceView||[1 0 0]||m||IC, MC||double|| |- |SourceView_Type||cartesian||m|||||| |- |SourceView_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 2b52783b6861a9dcf716a3f9846c0fe6086369be 186 185 2013-05-28T15:57:28Z Petibub 4 /* Proposed (for SOFA 0.4) */ wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This conventions defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SingleRoomDRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.0||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||reverberant||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_RoomDescription||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[1 0 1]||m||IC, MC||double|| |- |ListenerUp_Type||cartesian||m|||||| |- |ListenerUp_Units||meter||m|||||| |- |ListenerView||[0 0 0]||m||IC, MC||double|| |- |ListenerView_Type||cartesian||m|||||| |- |ListenerView_Units||meter||m|||||| |- |ListenerRotation||[0 0 0]||||IC, MC||double|| |- |ListenerRotation_Type||din9300|||||||| |- |ListenerRotation_Units||degrees|||||||| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceUp_Type||cartesian||m|||||| |- |SourceUp_Units||meter||m|||||| |- |SourceView||[1 0 0]||m||IC, MC||double|| |- |SourceView_Type||cartesian||m|||||| |- |SourceView_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 4966cb8dfb3cb5e9b1bb843b34e2fd214c11e61b 358 186 2013-06-20T13:39:33Z Petibub 4 updated to SOFA 0.4 draft version wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This conventions defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. ==Proposed (for SOFA 0.4)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SingleRoomDRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.0||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||reverberant||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_RoomDescription||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||||IC, MC||double|| |- |ListenerRotation_Type||din9300|||||||| |- |ListenerRotation_Units||degrees|||||||| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView||[1 0 0]||m||IC, MC||double|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 82ddbc08c999ea62348151cbb564101b5a71d6f4 0 11 355 80 2013-06-20T13:35:15Z Testente 7 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Download specifications version 0.3] * [[Proposal 0.4 | Draft proposal for specifications version 0.4]]: discuss with us the details of improvements you would like to see in the next SOFA version. * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Specifications version 0.2] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Specifications version 0.1 (as presented at the AES Convention 2013 in Rom)] a0080b6e0e6d9f30c018e7157829616194d1700e 0 17 383 101 2013-06-21T16:07:53Z Petibub 4 sofacoustics.org repository added wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The data from following projects are available at the moment: * [http://sofacoustics.org/data/database HRTFs for general purposes], databases like LISTEN, CIPIC, MIT KEMAR, ARI or TU-BERLIN are available * [http://sofacoustics.org/data/amt HRTFs] for the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo HRTFs] for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs cc30b573e3e0c417c68a7955a820ef34b10f3a2f 384 383 2013-06-21T16:08:48Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The data from following projects are available at the moment: * [http://sofacoustics.org/data/database HRTFs for general purposes], with databases like LISTEN, MIT KEMAR, or TU-BERLIN * [http://sofacoustics.org/data/amt HRTFs] for the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo HRTFs] for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs b9775a2f7d022ab8560047e95c8c9135d228d138 385 384 2013-06-21T16:09:16Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The data from following projects are available at the moment: * [http://sofacoustics.org/data/database HRTFs for general purposes], with databases like LISTEN, MIT KEMAR, or TU-BERLIN * [http://sofacoustics.org/data/amt HRTFs] for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo HRTFs] as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs 5826c07a5df2dd9b6916c1b7ffac8d6b5aa5426d 432 385 2013-06-25T15:05:22Z Petibub 4 description of repositories updated wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The following data are available at the moment: * [http://sofacoustics.org/data/database database] (HRTFs for general purposes]) ** [http://sofacoustics.org/data/database/listen listen] HRTFs from the LISTEN project ** [http://sofacoustics.org/data/database/ari ari] ARI database with the in-the-ear HRTFs and DTFs ** [http://sofacoustics.org/data/database/ari_bte ari_bte] ARI database with the behind-the-ear HRTFs and DTFs ** [http://sofacoustics.org/data/database/cipic cipic] CIPIC HRTF database ** [http://sofacoustics.org/data/database/mit mit] KEMAR HRTFs from MIT ** [http://sofacoustics.org/data/database/tu-berlin tu-berlin] HRTFs from TU-Berlin. * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs 47663f1a1d2c8e5d88041b46ab0e664f4b572ec5 1 463 391 2013-06-21T21:48:30Z 178.33.40.9 0 chatbox voor jongeren wikitext text/x-wiki chat online chatten ohne anmeldung http://www.ikchatmetvreemden.nl 4759a7a3febddf37288ab153ff6bb5157669bfaf 1463 391 2013-07-16T07:52:32Z 198.2.214.151 0 Arricaica Biopaybip Mulleyplutuat 41460 wikitext text/x-wiki NimaNemimup Whether you're looking justified to the happening that secluded out<a href="http://www.jtle.net/authentic-nfl-jerseys.html">cheap authentic jerseys</a> of sorts duds an eye to looking your to the fullest bounds at the games, tailgating threads to make a laughing-stock of your associate in colouring or you one desire to reveal I'm a buff like no other, NFL rags has on no reasoning smoke in more varieties or styles.Bring plot nightfall chili sessions to a unmistakeable budding match with an Passable<a href="http://www.jtle.net/authentic-nfl-jerseys.html">nfl authentic jerseys</a> NFL Jersey of your tie of stretched or impartial go hamlet in do to the Sunday cookouts with the guys.Football circumstance is in scrupulously ratchet and there's nothing like celebrating the span, supporting your troupe or<a href="http://www.jtle.net/authentic-nfl-jerseys.html">cheap nfl authentic jerseys</a> displaying your passion in hostility of the counterbalance up, like NFL jerseys.From carbon rendering jerseys, throwback jerseys or realized undisputed NFL Jerseys, to pullover sweatshirts, tank <a href="http://www.jtle.net/authentic-nfl-jerseys.html">authentic nfl jerseys</a>tops, eyewash pajamas, hat and beanies you can advocate your duo and at all that football palatable entails with NFL Sports Apparel. http://www.dailyqr.com/blog_entry.php?user=390234&blogentry_id=4511346 http://www.wahabox.com/uchome/space.php?uid=13543&do=blog&id=82807 http://www.yuexicn.com/blog/space.php?uid=31595&do=blog&id=62426 http://bbs.goodguanjia.com/forum.php?mod=viewthread&tid=5035034 http://scholand.de/mediawiki/index.php?title=User:Jdmr1260#That_which_we_enjoy._He_can_say_to_an_account. 129b34342dc646f147dbd6716bd381cdd1aa41f3 1655 1463 2013-07-18T16:53:44Z 27.153.248.252 0 detailnews wikitext text/x-wiki Japan-based JFE chemical has lowered operating rates at its two benzene plants. "The benzene plant located in Kasaoka is running at 60 percent capacity prices and the Chiba plant is operating at 50 % production rates", a JFE official told fibre2fashion "Our operating rates are dependent on provide and price tag trends of Crude benzene derived from coke ", he revealed when asked regarding the reason behind lowering prices. When quizzed on upcoming maintenance schedules, he said," Turnaround at the Kasaoka plant would take location in April 2013 and in Chiba, it's probably to come about in October 2013. "Each of your benzene plants has a capacity of 110,000 tons per annum. http://jjyy.freeiz.com/forum.php?mod=viewthread&tid=180904&extra= 537f838c846faa42e79a5bbaaafbcb8049ea6d8f 1 19 437 195 2013-06-25T16:22:01Z Petibub 4 informative part removed, attributes proposed wikitext text/x-wiki == Headphone transfer functions (HpTFs) == No public HpIR databases nor standard HpIR repositories have been proposed to date. One of the purposes of HpIRs recordings is to compute the equalization filter that compensates the headphone starting from the raw HpIRs. ''Question: store the full transmitter-receiver matrix or only a one-to-one correspondence?'' For each pair of headphones, a collection of individual HpIRs and equalization filters are stored with respect to a specific subject. ''SubjectID seems to be required. Saved as equalization filters, the data could have a one-to-one correspondence between transmitters and receivers, i.e., data for each receiver correspond to data for a transmitter.'' It is desirable to have a ''foreign key'' to the HRIRs set recorded on the same subject in order to provide data for an individual binaural listening experience. For every subject, three data containers - raw, compensated and eq - could be defined. ''The processing state could be defined by the global attribute ProcessingState'': * the raw data from the recordings: ''GLOBAL_ProcessingState = 'raw'?'' * the compensated impulse responses: ''GLOBAL_ProcessingState = 'compensated by using xxx algorithm with yyy parameters'?'' * the equalization filter (under the form of an impulse response) obtained from the inverse HpIR through one or more techniques, e.g. considering the mean HpIR measurement with respect to all the repositionaments of that device. ''This could be also described by the ProcessingState, e.g., GLOBAL_ProcessingState = 'inverted equ filters by using XXX regularization and YYY averaging technique'.'' The following information is required: * headphone model, producer. ''This could correspond to SourceDescription and TransmitterDescription''. Specific characteristics of the headphones such as transducer type, acoustic coupling, and design are stored in their data sheet. * eq algorithm, equalization algorithm used. ''ProcessingState could be used as a narrative descriptor.'' == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". * Seems like we need a good definition of "raw", "processed", and "un-calibrated". Then we could provide an attribute, e.g., ProcessingState. Otherwise, we could use "ProcessingState" in the same way we use "Comments", namely, include a narrative description of the processing steps. Then we could write GLOBAL_ProcessingState = "Deconvolution with exp. sweep, windowing at ..., filtering at..." and so on. Applications which do not care, could ignore it; researchers who care could interpret it. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. * It seems like we would need to save the IRs from speaker(s) and microphone(s) together with other metadata like levels. Would it be sufficient to store that information in a separate SOFA file? Applications which do not care, would not have this ballast. Researchers who care, could use it to reproduce all post-processing steps. A new SOFA conventions for calibration would do - Does it make sense? * Seems like level would be important. Intermediate results: specifications for the level required, name for the variable required? Then, we could have level as an optional variable in SOFA. Also, some data would be nice == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 6833e1e29dccc6814ebd82b5133cee30dd5a45ba 438 437 2013-06-25T16:24:08Z Petibub 4 wikitext text/x-wiki == Headphone transfer functions (HpTFs) == No public HpIR databases nor standard HpIR repositories have been proposed to date. One of the purposes of HpIRs recordings is to compute the equalization filter that compensates the headphone starting from the raw HpIRs. ''Question: store the full emitter-receiver matrix or only a one-to-one correspondence?'' For each pair of headphones, a collection of individual HpIRs and equalization filters are stored with respect to a specific subject. ''SubjectID seems to be required. Saved as equalization filters, the data could have a one-to-one correspondence between emitters and receivers, i.e., data for each receiver correspond to data for a emitter.'' It is desirable to have a ''foreign key'' to the HRIRs set recorded on the same subject in order to provide data for an individual binaural listening experience. For every subject, three data containers - raw, compensated and eq - could be defined. ''The processing state could be defined by the global attribute ProcessingState'': * the raw data from the recordings: ''GLOBAL_ProcessingState = 'raw'?'' * the compensated impulse responses: ''GLOBAL_ProcessingState = 'compensated by using xxx algorithm with yyy parameters'?'' * the equalization filter (under the form of an impulse response) obtained from the inverse HpIR through one or more techniques, e.g. considering the mean HpIR measurement with respect to all the repositionaments of that device. ''This could be also described by the ProcessingState, e.g., GLOBAL_ProcessingState = 'inverted equ filters by using XXX regularization and YYY averaging technique'.'' The following information is required: * headphone model, producer. ''This could correspond to SourceDescription and EmitterDescription''. Specific characteristics of the headphones such as transducer type, acoustic coupling, and design are stored in their data sheet. * eq algorithm, equalization algorithm used. ''ProcessingState could be used as a narrative descriptor.'' == Include anthropometric data (AD) == Several request received on "include AD in SOFA". But none of them could specify what actually to store. What is clear that AD stored with CIPIC are not sufficient. In ARI more AD are store than in CIPIC, but there is no proof that these AD are of any use. So? == Crosstalk cancellation filters (CTCFs) == When saving HRTFs, why not save CTCFs? Check and discuss how the representation of CTCFs differs from the representation of HRTFs. It might be that SimpleFreeFieldHRIR is sufficient and the difference between HRTFs and CTCFs is simple the interpretation. Then, a note in GLOBAL_Comment might be sufficient. At the same time, the calculation and use of CrossTalk cancellation filters goes beyond a general SOFA dataset. One can of course calculate the CTCFs filter if one wants, using various methods, but it is by no means an inherent part of the measured data, and more an application specific post-processing tool for a specific installation. It is, of course, also dependent on the speaker positions of the playback system chosen, and therefore this information should be stored within SOFA if required. It seems like more information from researchers about their requirements is required. == Include calibration data == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the calibration? Corresponding researchers contacted, waiting for response... Calibration data can hav several forms, depending on the measurement in question. If the measurement is a transfer function, and that it it's intention, then one could provide the measured transfer function of the measurement chain without the measurement object present. In the case of the HRTF, this is the measured transfer function without the head present. As there are various means of removing the effects of the measurement chain (deconvolution, spectral equalizing) the "calibrated" final data may vary between methods. If the object if to provide the data in its most raw form, for other researchers to use, the uncalibrated data, along with necessary calibration files, is of interest. In this way, the frequency response of the key elements, notably the microphone and speakers, can be both examined and taken into account. In the context of HRTF measurements which use multiple speakers, the calibration of each speaker is crucial in order to avoid spectral coloration which is independent of the head response and therefor an artifact of the measurement system. In such a case, impulse responses should be provided for each speaker, with the microphone oriented on-axis to the speaker. This can be performed with the measurement microphones used for the data acquisition, or a calibrated measurement microphone, whose model should be clearly stated. If the second is employed, a microphone measurement file is also necessary, consisting of a calibration measurement for a single speaker and the accompanying impulse response of all 3 microphones (again, in the case of and HRTF measurement). For a truly robust analysis of the data, this calibration measurement is made before and after the measurement session, to ensure no time independence of the measurement system, which is not always the case. In such a case that the before/after data do not correspond, the data should not be utilized. The actual data to be included is therefore a simple impulse response clearly annotated to indicate the microphone/speaker in question. This therefore requires in a multi-speaker measurement condition that each entry in the HRTF set includes a speaker ID. In the event that "un-calibrated", or already calibrated processed data, is provided, then there should be a clear text description indicating the calibration method used, and any addition post-treatment, such as low-frequency interpolated data (how, frequency range), equalization (diffuse field or otherwise), etc. As these different elements are clearly of more interest to researchers, rather than industrial uses, they cannot be "required elements". A simple required tag should be available indicating if the data is "raw" with accompanying calibration data, or is "processed". * Seems like we need a good definition of "raw", "processed", and "un-calibrated". Then we could provide an attribute, e.g., ProcessingState. Otherwise, we could use "ProcessingState" in the same way we use "Comments", namely, include a narrative description of the processing steps. Then we could write GLOBAL_ProcessingState = "Deconvolution with exp. sweep, windowing at ..., filtering at..." and so on. Applications which do not care, could ignore it; researchers who care could interpret it. In the case of measurements where the absolute level is of importance, the calibration data is more typically that of a piston/speaker phone which provides a known SPL level. This is of specific interest when distributed microphones are employed to measure the spatial distribution of a sound field. In this instance, the calibration data can either be the noted RMS level of the calibrated source for each microphone (noting of course the model and settings of the calibrated source, and if possible, meterological conditions). To be consistent with the above mentioned HRTF case, the recorded calibration audio file could be provided, again noting the model and settings used. * It seems like we would need to save the IRs from speaker(s) and microphone(s) together with other metadata like levels. Would it be sufficient to store that information in a separate SOFA file? Applications which do not care, would not have this ballast. Researchers who care, could use it to reproduce all post-processing steps. A new SOFA conventions for calibration would do - Does it make sense? * Seems like level would be important. Intermediate results: specifications for the level required, name for the variable required? Then, we could have level as an optional variable in SOFA. Also, some data would be nice == Include room pictures == * Are data available? * Is a description of the measurement setup available? * What metadata should be stored? * How to standardize the description of the pictures (camera position, room description)? There is [http://en.wikipedia.org/wiki/FITS FITS] for astronomy maybe we can learn from this format? Corresponding researchers contacted, waiting for response... 5fb5cd181aaab2598c4f76226ff68e68b57c59c2 0 18 439 193 2013-06-25T16:44:34Z Petibub 4 /* Mandatory metadata */ wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == We propose the following metadata to be mandatory for '''all''' SOFA conventions. Following rules must be fulfilled: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Various issues == === Versioning of SOFA and conventions === Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. === Allow various DataTypes within a single SOFAConventions? === * Fixed DataType: ** Pro: very simple for applications: they just have to check the conventions and the data type is known. ** Con: separate conventions for each DataType required even though the measurement setup might have not changed. * Arbitrary DataType allowed: ** Pro: less conventions, we will have conventions which do not consider the datatype. ** Con: Each application has either to provide '''all''' datatypes and branch while processing between the different algorithms, or to check both Conventions '''and''' DataType on loading. At the moment we have 1 stable and 2 proposed SOFA Conventions. This number is rather low, thus we wait until we'll have more conventions and then decide if we want to allow to separate DataType from SOFAConventions. === Fix the coordinate systems within conventions? === Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. === Naming of the units === lowercase, the rest is not clarified yet. === Include strings as variables === === Role of dimension variables === At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == DataType == === New: IIRBiquad === {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} === New: ComplexSpectrum === {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. === Update: FIR === The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. b923e29d002e5d3488e5e0edff156d7aaef3060c 700 439 2013-06-29T15:30:46Z Petibub 4 Renamed ComplexSpectrum to TF wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' '''Please discuss the proposal by using the "Discussion" function of Wiki.''' == Mandatory metadata == We propose the following metadata to be mandatory for '''all''' SOFA conventions. Following rules must be fulfilled: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Various issues == === Versioning of SOFA and conventions === Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. === Allow various DataTypes within a single SOFAConventions? === * Fixed DataType: ** Pro: very simple for applications: they just have to check the conventions and the data type is known. ** Con: separate conventions for each DataType required even though the measurement setup might have not changed. * Arbitrary DataType allowed: ** Pro: less conventions, we will have conventions which do not consider the datatype. ** Con: Each application has either to provide '''all''' datatypes and branch while processing between the different algorithms, or to check both Conventions '''and''' DataType on loading. At the moment we have 1 stable and 2 proposed SOFA Conventions. This number is rather low, thus we wait until we'll have more conventions and then decide if we want to allow to separate DataType from SOFAConventions. === Fix the coordinate systems within conventions? === Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. === Naming of the units === lowercase, the rest is not clarified yet. === Include strings as variables === === Role of dimension variables === At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == DataType == === New: IIRBiquad === {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} === New: TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. === Update: FIR === The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. d016265667c2ecc352b3e37c1ede44f754b69f23 0 5 701 187 2013-06-29T15:31:13Z Petibub 4 /* Proposed SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldHRIR]]: adaptation of the previous version of SimpleFreeFieldHRIR for SOFA 0.4 * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Headphone transfer functions: data exist, need more information on metadata * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! ca04a9a7526a89f0ea44289c4b5e0825efea581e 703 701 2013-06-29T15:37:36Z Petibub 4 GeneralTF and GeneralFIR added wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldHRIR]]: adaptation of the previous version of SimpleFreeFieldHRIR for SOFA 0.4 * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space * ([[GeneralFIR]]): General convention with TF as DataType (no restrictions but DataType) * ([[GeneralTF]]): General convention with FIR as DataType (no restrictions but DataType) == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Headphone transfer functions: data exist, need more information on metadata * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! e1f5fda191f28b4749ed7f7cd8641d21f5786a75 836 703 2013-07-12T08:56:38Z Petibub 4 SimpleFreeFieldHRIR 0.3 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldHRIR]]: adaptation of the previous version of SimpleFreeFieldHRIR (proposed as version 0.3) * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space * ([[GeneralFIR]]): General convention with TF as DataType (no restrictions but DataType) * ([[GeneralTF]]): General convention with FIR as DataType (no restrictions but DataType) == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Headphone transfer functions: data exist, need more information on metadata * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 1475c561cd586d0d9e785aff1d781502c99e7ee2 0 24 702 357 2013-06-29T15:31:46Z Petibub 4 wikitext text/x-wiki This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is TF. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. ==Proposed for SOFA 0.4== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldTF||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.1||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency|||||||| |- |N_Units||hertz|||||||| |} 8536a6778c9408c34a6c6e6692210a44a2edf943 0 286 704 2013-06-29T15:41:09Z Petibub 4 Created page with "This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too ge..." wikitext text/x-wiki This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * the configuration of sources and receivers in a BEM simulation, * raw data of headphone measurements a1cda490c72b8353ae6e08797820c27efb52f9ab 705 704 2013-06-29T15:41:49Z Petibub 4 wikitext text/x-wiki This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements ee20b1cf66fa4317a87f63a5a74637c27f478a65 0 287 706 2013-06-29T15:42:38Z Petibub 4 Created page with "This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too gene..." wikitext text/x-wiki This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. 25fda85c7299081307853e89a9f92a94bdc4e173 0 1 712 138 2013-06-29T17:38:13Z Noisternig 5 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 0f5eb1513039275fe330e2bd1761c83efcc8d4b7 714 712 2013-06-29T17:39:45Z Noisternig 5 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize [http://soundsoftware.ac.uk/rr-prize-winner-announcement] 2013. 5d53c7f8f68f0d63332ba64ca7d71205bf08f2c3 715 714 2013-06-29T17:40:07Z Noisternig 5 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 4dd918883101847f01a31aec42063c62840a82fc 1669 715 2013-07-18T18:44:50Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 67e19994edeff544591e4d5f62fa48c733151f95 1670 1669 2013-07-18T18:49:12Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 9ebf30d6f20c1a15236f956f77bdbf6819d811ca 1671 1670 2013-07-18T18:49:56Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. ^ a7a4c409d2c24d9658a88444a3b97a8083a8bdf1 1672 1671 2013-07-18T18:51:18Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 9ebf30d6f20c1a15236f956f77bdbf6819d811ca 1673 1672 2013-07-18T18:53:20Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 67e19994edeff544591e4d5f62fa48c733151f95 1674 1673 2013-07-18T18:54:35Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 9ebf30d6f20c1a15236f956f77bdbf6819d811ca 1675 1674 2013-07-18T18:56:58Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 67e19994edeff544591e4d5f62fa48c733151f95 1676 1675 2013-07-18T18:58:27Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 9ebf30d6f20c1a15236f956f77bdbf6819d811ca 1677 1676 2013-07-18T19:04:05Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 270a7b0e89e03e363d48bc421c8023e31c39d21b 1678 1677 2013-07-18T19:06:23Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 69837abf50b3d926e24f20158f21d890dd64d276 1683 1678 2013-07-19T20:28:48Z Ente 1 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 1845199a410a364f43fac479624754f037a34087 0 9 835 382 2013-07-12T08:43:26Z Petibub 4 version 0.4 added wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[0 1 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). == Stable (version 0.2) == [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 1c0f14dc1d4885ae4731525a81aa89cc3c271948 837 835 2013-07-12T09:08:44Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). == Stable (version 0.2) == [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) bd0934bceb3a5a66f62149b5b476e9c2db2dfff6 1276 837 2013-07-15T17:13:48Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |APV||[0 0 0]||m||IC, MC||double|| |- |APV_Type||spherical||m|||||| |- |APV_Units||degree, degree, meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} == Stable (version 0.2) == [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 55dbfcc6534d2a49f84217a8960a3201702c4c62 1278 1276 2013-07-15T17:18:16Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |APV||[0 0 0]||m||IC, MC||double||Apparent Position Vector: HRTF position/direction as the interpretation of the geometry for applications |- |APV_LongName||apparent position vector||m|||||| |- |APV_Type||spherical||m|||||| |- |APV_Units||degree, degree, meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} == Stable (version 0.2) == [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ae4983309b2698ae6dfe85fd5c1b1a053d5a2f9d 1280 1278 2013-07-15T17:19:27Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |APV||[0 0 0]||m||IC, MC||double||Apparent Position Vector: HRTF position/direction as the interpretation of the geometry for applications |- |APV_LongName||apparent position vector||m|||||| |- |APV_Type||spherical||m|||||| |- |APV_Units||degree, degree, meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 0e1222893f16f6be144e2447143a019cdbd09c9d 1281 1280 2013-07-15T17:49:26Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRTF_0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |APV||[0 0 0]||m||IC, MC||double||Apparent Position Vector: HRTF position/direction as the interpretation of the geometry for applications |- |APV_LongName||apparent position vector||m|||||| |- |APV_Type||spherical||m|||||| |- |APV_Units||degree, degree, meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 87cbef9c995cc19e854a0ae4d682169e09acc868 1451 1281 2013-07-16T06:40:38Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRTF-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |APV||[0 0 0]||m||IC, MC||double||Apparent Position Vector: HRTF position/direction as the interpretation of the geometry for applications |- |APV_LongName||apparent position vector||m|||||| |- |APV_Type||spherical||m|||||| |- |APV_Units||degree, degree, meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 6dd3bcfc1b9094f5dd8f2f8f03b3fa95cc4fb67d 1453 1451 2013-07-16T06:44:06Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |APV||[0 0 0]||m||IC, MC||double||Apparent Position Vector: HRTF position/direction as the interpretation of the geometry for applications |- |APV_LongName||apparent position vector||m|||||| |- |APV_Type||spherical||m|||||| |- |APV_Units||degree, degree, meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRTF.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 99c6f4a16948aeaa23e732141d3acce2b976472c 1455 1453 2013-07-16T06:44:30Z Petibub 4 /* Stable (version 0.2) */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |APV||[0 0 0]||m||IC, MC||double||Apparent Position Vector: HRTF position/direction as the interpretation of the geometry for applications |- |APV_LongName||apparent position vector||m|||||| |- |APV_Type||spherical||m|||||| |- |APV_Units||degree, degree, meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRIR.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) e87e860141629c0d42e6c3f6be7f3a796272ea17 1456 1455 2013-07-16T06:45:06Z Petibub 4 /* Stable (version 0.2) */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |APV||[0 0 0]||m||IC, MC||double||Apparent Position Vector: HRTF position/direction as the interpretation of the geometry for applications |- |APV_LongName||apparent position vector||m|||||| |- |APV_Type||spherical||m|||||| |- |APV_Units||degree, degree, meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 04f52de86a81228e5b4067741d4f58ec7a93ea2b 1680 1456 2013-07-19T05:46:09Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. * Further, the different azimuth and elevation angles of the measurement are described by the apparent position vector, APV, in spherical coordinates (azimuth, elevation, radius). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 769c122b8af632bec4026bdc3af3edeb5510bb7e 1681 1680 2013-07-19T05:46:34Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm||||||Must be always SOFA |- |GLOBAL_Version||0.4||rm||||||Describes the SOFA version |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m||||||The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title||||m||||||A succinct description of what is in the dataset |- |GLOBAL_References||||m||||||Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Listener is assumed to be in the center of the measurement setup |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition_Type||spherical||m|||||| |- |SourcePosition_Units||degree, degree, meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm||||||Describes the SOFA Conventions |- |GLOBAL_SOFAConventionsVersion||0.3||rm||||||Describes the version of the Conventions |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m||||||name of the database to which these data belong |- |GLOBAL_SubjectID||||m||||||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 9a9ea2b4406dde89d1c5a7709827f9947a2b04b4 6 416 1458 2013-07-16T06:51:45Z Petibub 4 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1684 1458 2013-07-26T11:01:37Z Petibub 4 Petibub uploaded a new version of &quot;[[File:SimpleFreeFieldHRIR-0.3.png]]&quot; wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1685 1684 2013-07-26T11:02:32Z Petibub 4 Petibub uploaded a new version of &quot;[[File:SimpleFreeFieldHRIR-0.3.png]]&quot; wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1686 1685 2013-07-26T11:03:31Z Petibub 4 Petibub uploaded a new version of &quot;[[File:SimpleFreeFieldHRIR-0.3.png]]&quot;: Reverted to version as of 11:01, 26 July 2013 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 417 1459 2013-07-16T06:56:31Z Petibub 4 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 14 1642 141 2013-07-18T15:05:51Z 31.184.238.68 0 /* Common Data Form Language (CDL) */ wikitext text/x-wiki JsAMWR <a href="http://vshuibtskptq.com/">vshuibtskptq</a>, [url=http://sptpzllzqlsc.com/]sptpzllzqlsc[/url], [link=http://zbcqxedsudpq.com/]zbcqxedsudpq[/link], http://rwonoussprgn.com/ == HDF5View == SOFA files can be loaded and edited in the [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] - a viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files. Note that SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4], which is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. c92aa71b244b6b86375d6c9578f494ffec13ef46 0 18 1687 700 2013-08-20T13:36:02Z Petibub 4 Closing 0.4 wikitext text/x-wiki '''Only changes compared to the last version are listed here!!!''' == Mandatory metadata == We propose the following metadata to be mandatory for '''all''' SOFA conventions. Following rules must be fulfilled: * Mandatory because without this metadata '''any''' conventions will fail * Or, mandatory because users might forget it, resulting in inconsistencies for '''all''' conventions {| border="1" !Name !Default !Read-Only !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||r|| || || |- |GLOBAL_Version|| ||r|||| || Insert the actual SOFA version here |- |GLOBAL_SOFAConventions|| || |||| || Insert the name of the actual SOFA Conventions here |- |GLOBAL_SOFAConventionsVersion|| |||||||| Insert the actual SOFA convention version here |- |GLOBAL_APIName|| || || |||| Insert the API Name here |- |GLOBAL_APIVersion|| || || |||| Insert the API Version here |- |GLOBAL_AuthorContact|||| |||||| |- |GLOBAL_License||No license provided, ask the author for permission|| |||| || |- |GLOBAL_Organization|||| |||| || |- |GLOBAL_RoomType||free field|| |||| || |- |GLOBAL_DataType||FIR|| |||| || Insert the name of the actual datatype here |- |GLOBAL_History|||||||| || |- |GLOBAL_Source|||||||||| The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it. |- |GLOBAL_Title|||||||||| A succinct description of what is in the dataset |- |GLOBAL_References|||||||| || Published or web-based references that describe the data or methods used to produce it |- |GLOBAL_Comment|||||||| || |- |GLOBAL_TimeCreated|| || |||| || will be updated when saving and not existing or empty |- |GLOBAL_TimeModified|| || |||||| will be updated each time when saving |- |ListenerPosition|| [1 0 0] ||||IC, MC|| double || |- |ListenerPosition_Type||cartesian|||| || || |- |ListenerPosition_Units||meter|||||| || |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||||rCI, rCM|| double || |- |ReceiverPosition_Type||cartesian|||||| || |- |ReceiverPosition_Units||meter|| |||||| |- |SourcePosition||[0 0 0]||||IC, MC||double || |- |SourcePosition_Type||cartesian|||||| || |- |SourcePosition_Units||meter|| |||||| |- |EmitterPosition||[0 0 0]||||eCI, eCM||double || |- |EmitterPosition_Type||cartesian|||||| || |- |EmitterPosition_Units||meter|||||| || |} Note: we consider the Data as mandatory, thus, Data must be provided according the corresponding DataType. If DataType is default (="FIR") then Data for the datatype "FIR" must be provided. Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value and must not be changed * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) * '''Type''': type of the data, i.e., double, string, etc. Empty if attribute '''Dimensional variables (coordinate variables)''': At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. == Various issues == === Versioning of SOFA and conventions === Three version types: * Version: defines the version of the general SOFA specs * ConventionsVersion: defines the version of the particular SOFA conventions. Could be merged with Version, but then, when we change something a Conventions, each time the version for the general SOFA specs would need to be increased. Not clear how to proceed. Maybe the AES standardization process will clarify. Until then: no merging, to be on the safe side. * APIVersion: clearly separated from the rest. === Allow various DataTypes within a single SOFAConventions? === * Fixed DataType: ** Pro: very simple for applications: they just have to check the conventions and the data type is known. ** Con: separate conventions for each DataType required even though the measurement setup might have not changed. * Arbitrary DataType allowed: ** Pro: less conventions, we will have conventions which do not consider the datatype. ** Con: Each application has either to provide '''all''' datatypes and branch while processing between the different algorithms, or to check both Conventions '''and''' DataType on loading. At the moment we have 1 stable and 2 proposed SOFA Conventions. This number is rather low, thus we wait until we'll have more conventions and then decide if we want to allow to separate DataType from SOFAConventions. === Fix the coordinate systems within conventions? === Until now, Conventions support just a single coordinate system per variable and each application must use conversion functions if required. === Naming of the units === lowercase, the rest is not clarified yet. === Include strings as variables === === Role of dimension variables === At the moment, we consider the dimension variables (or coordinate variables) as not mandatory, i.e., optional. Depending on the datatype and conventions, some of them might be mandatory, though. We suggest the type "double" for the dimensional variables. If provided, use also attributes to describe the LongName and Units. == DataType == === New: IIRBiquad === {| border="1" !Name !Default !Dimensions !Comment |- |Data.G|| 1 ||MR|| broadband linear gain |- |Data.B1|| || MRN || nominator coefficient B1 |- |Data.B2|| || MRN || nominator coefficient B2 |- |Data.A1|| || MRN || denominator coefficient A1 |- |Data.A2|| || MRN || denominator coefficient A2 |- |Data.Delay|| 0 || MR || broadband delay |- |Data.SamplingRate|| 48000 || I || Sampling rate of the filter coefficients and the delay |- |Data.SamplingRate_Units||hertz|| || |} === New: TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.Real|| 1 ||mRn|| double || real part of the complex spectrum |- |Data.Imag|| 0 || MRN || double || imaginary part of the complex spectrum |- |N|| 0 || N || double || frequency values |- |N_LongName|| frequency || || || |- |N_Units|| hertz || || || |} Note that the dimensional variable N is mandatory, must be of dimension N, and must provide the frequency values. === Update: FIR === The standard committee agreed that the broadband delay should be provided in any case. Thus, we propose to add a new field, Delay to the FIR type. {| border="1" !Name !Default !Dimensions !Type !Comment |- |Data.IR|| 1 ||mRn|| double || impulse responses |- |Data.Delay|| 0 || IR, MR || double || broadband delay |- |Data.SamplingRate|| 48000 || I || double || Sampling rate of the IRs and the delay |- |Data.SamplingRate_Units||hertz|| || || |} == RoomType == We propose the following RoomTypes. Note that any other RoomType than freefield means that reverberation is expected to be in the data. === freefield === * Meaning: Data measured under assumed freefield conditions. * Usage: Used for the most of the HRTF databases. * Parameters: ** RoomDescription: optional, narrative description of the anechoic chamber used. === reverberant === * Meaning: don't know, don't care * Usage: Default value. * Parameters: ** RoomDescription: optional, narrative description of the room === shoebox === * Meaning: Rectangular room for which the size is known. Can be used as a first-order approximation of the room. * Usage: BRIRs from Oldenburg measured in Office II are using that RoomType. * Parameters: ** RoomCornerA: mandatory, [C], defines the first room corner. Provide Type and Units as well. ** RoomCornerB: mandatory, [C], defines the second room corner. Provide Type and Units as well. ** RoomDescription: optional, narrative description of the room. === link === * Meaning: Quantitative room description is provided in a separate file. This RoomType was "DAE" in previous SOFA versions, but I think that "link" is more general. * Usage: Not used yet. * Parameters: ** GLOBAL_RoomLink: mandatory, provides a link to the file. More details must be defined on the first appearance of usage. ** RoomDescription: optional, narrative description of the room. 66be9d26766c2155b4ba0180ed2be8daf4b781dc 0 11 1688 355 2013-08-20T13:38:08Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Download specifications version 0.3] * [[Proposal 0.4 | Discussion on the specifications 0.4]] (closed) * [[Proposal 0.5 | Draft proposal for specifications version 0.5]]: discuss with us the details of improvements you would like to see in the next SOFA version. * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Specifications version 0.2] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Specifications version 0.1 (as presented at the AES Convention 2013 in Rom)] 02b11497824d33a92e1a09ea98995b422f5a3794 1689 1688 2013-08-20T13:45:11Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [[http://sourceforge.net/p/sofacoustics/code/186/tree/trunk/doc/SOFA%20specs%200.5.fodt Version 0.5: Draft proposal in Subversion on SourceForge]] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] cf1b6417ba9a1fd952c82efefdc38fb420a7ac0e 1700 1689 2013-08-30T09:07:27Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] 7080aa85d93ec0e062c555427b7bcf95e0a82280 1710 1700 2014-03-20T17:08:04Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.5: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] bf147c75570e438e3d3c5fcf79730020ac7bd473 1711 1710 2014-03-20T17:08:16Z Petibub 4 wikitext text/x-wiki * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] 1eef50d4b12c0e95e0284ff57f3b84c75ed6f65a 0 9 1690 1681 2013-08-20T13:49:48Z Petibub 4 /* Proposed for version 0.3 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Stable (version 0.2) == [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) d6bdcbcab26ac90ebb3cbeb6e00535c2f8113081 1698 1690 2013-08-20T13:59:30Z Petibub 4 /* Stable (version 0.2) */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Unused (version 0.2) == [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 4a35b70953017be422789df93b1a24354d829f38 1712 1698 2014-03-20T17:16:12Z Petibub 4 /* Description */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the currently most recent version, we adapted the Conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Unused (version 0.2) == [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) d7ba5d412ce0f9353d5afdbe424df7fe40328b91 1713 1712 2014-03-20T17:18:48Z Petibub 4 SimpleFreefieldHRIR 0.4 added wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the currently most recent version, we adapted the Conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). == Version 0.4 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Proposed for version 0.3 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Unused (version 0.2) == [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ==Stable (version 0.1)== {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 2d5a098e8d62c73ade205fe3a7a59f7609e49c30 0 24 1691 702 2013-08-20T13:51:38Z Petibub 4 /* Proposed for SOFA 0.4 */ wikitext text/x-wiki This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is TF. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. ==Proposed as 0.3 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} f45f3161b93cc2a501b4342ad151ef5292caa728 1714 1691 2014-03-20T17:20:23Z Petibub 4 wikitext text/x-wiki This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is TF. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. ==Proposed as 0.4 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldTF||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} == Deprecated as 0.3 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} 78b6f2ef877fdcc3dafcca77e76a821b247da4f3 0 25 1692 358 2013-08-20T13:52:32Z Petibub 4 /* Proposed (for SOFA 0.4) */ wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This conventions defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. ==Proposed (for SOFA 0.5)== {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomDRIR||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||reverberant||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute|| |- |GLOBAL:RoomDescription||||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView||[-1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} a5cd452da331235bbec1a4996bfc31bb8f2d5c3e 0 5 1693 836 2013-08-20T13:53:32Z Petibub 4 /* Proposed SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[GeneralFIR]]: General convention with TF as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with FIR as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: adaptation of the previous version of SimpleFreeFieldHRIR (proposed as version 0.3) * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Headphone transfer functions: data exist, need more information on metadata * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 864136b415e933d6688103811a97923ed4c3fe93 1694 1693 2013-08-20T13:54:56Z Petibub 4 /* Proposed SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[GeneralFIR]]: General convention with TF as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with FIR as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: adaptation of the previous version of SimpleFreeFieldHRIR (proposed as version 0.3) * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[HeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Headphone transfer functions: data exist, need more information on metadata * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! cc962da3f2540c222846b5704dce66621b543fb1 1697 1694 2013-08-20T13:56:50Z Petibub 4 /* Unsorted topics */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[GeneralFIR]]: General convention with TF as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with FIR as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: adaptation of the previous version of SimpleFreeFieldHRIR (proposed as version 0.3) * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[HeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 4d5fa37a271e25327c8d2c4865fc2d06b6c2ce3c 1708 1697 2014-02-25T13:38:59Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with TF as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with FIR as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[HeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 1820494bf7961b78025221e5bb7ac5f7736674e5 0 459 1695 2013-08-20T13:55:50Z Petibub 4 Created page with "Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and..." wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == 8da9360cafe1424d67cfce75b88829e252b687f9 1696 1695 2013-08-20T13:56:06Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 2002225c7fc7f8b408ac4cb1d88821d2785dafe4 1730 1696 2014-06-13T13:42:06Z Petibub 4 wikitext text/x-wiki '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} dda30fc311dab8793aac1fe783d42d1ff280acdb 1735 1730 2014-06-13T14:04:31Z Petibub 4 wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} dbd61117cdc4ab57fde6f042ae4f7644d343534a 0 17 1699 432 2013-08-29T12:09:04Z Petibub 4 /* Main SOFA repository */ wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The following data are available at the moment: * [http://sofacoustics.org/data/database database] (HRTFs for general purposes]) ** [http://sofacoustics.org/data/database/listen listen] HRTFs from the LISTEN project ** [http://sofacoustics.org/data/database/ari ari] ARI database with the in-the-ear HRTFs and DTFs ** [http://sofacoustics.org/data/database/ari_bte ari_bte] ARI database with the behind-the-ear HRTFs and DTFs ** [http://sofacoustics.org/data/database/cipic cipic] CIPIC HRTF database ** [http://sofacoustics.org/data/database/mit mit] KEMAR HRTFs from MIT ** [http://sofacoustics.org/data/database/tu-berlin tu-berlin] HRTFs from TU-Berlin. ** [http://sofacoustics.org/data/database/oldenburg oldenburg] '''DRIRs''' from Oldenburg * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs 59667367a45c1b17762685ddc3dbddb7f87dac4d 1702 1699 2013-11-18T13:13:24Z Petibub 4 FHK added wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The following data are available at the moment: * [http://sofacoustics.org/data/database database] (HRTFs for general purposes]) ** [http://sofacoustics.org/data/database/listen listen] HRTFs from the LISTEN project, IRCAM. ** [http://sofacoustics.org/data/database/ari ari] ARI database. In-the-ear HRTFs and DTFs for over 100 listeners. ** [http://sofacoustics.org/data/database/ari_bte ari_bte] ARI database. Behind-the-ear HRTFs and DTFs. ** [http://sofacoustics.org/data/database/cipic cipic] CIPIC HRTF database. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/mit mit] KEMAR HRTFs from MIT. Reference measurements of a dummy head. ** [http://sofacoustics.org/data/database/tu-berlin tu-berlin] HRTFs from TU-Berlin of the dummy-head KEMAR. Several distances. ** [http://sofacoustics.org/data/database/oldenburg oldenburg] '''DRIRs''' from Oldenburg. Recordings in an office under several conditions. ** [http://sofacoustics.org/data/database/fhk fhk] '''HRTFs''' from the Fachhochschule Köln of the dummy-head Neumann K100. High spatial resolution. * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs daba3a9ce5b3ed2f0d998bd8343fe84ea6f88296 1703 1702 2013-11-18T13:25:05Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The following data are available at the moment: * [http://sofacoustics.org/data/database database] (HRTFs for general purposes]) ** [http://sofacoustics.org/data/database/listen listen] HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/ari ari] HRTF from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** [http://sofacoustics.org/data/database/ari_bte ari_bte] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. Behind-the-ear HRTFs and DTFs. ** [http://sofacoustics.org/data/database/cipic cipic] HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/mit mit] HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** [http://sofacoustics.org/data/database/tu-berlin tu-berlin] HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances. ** [http://sofacoustics.org/data/database/oldenburg oldenburg] '''DRIRs''' from [http://sirius.physik.uni-oldenburg.de/downloads/hrir/ Oldenburg]. Recordings in an office under several conditions. ** [http://sofacoustics.org/data/database/fhk fhk] '''HRTFs''' from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. High spatial resolution provided. * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs 1f26151f6960bf11480739827c8cabf4555dc4e3 1704 1703 2013-11-18T13:25:45Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The following data are available at the moment: * [http://sofacoustics.org/data/database database] (HRTFs for general purposes]) ** [http://sofacoustics.org/data/database/listen listen] HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/ari ari] HRTF from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** [http://sofacoustics.org/data/database/ari_bte ari_bte] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. Behind-the-ear HRTFs and DTFs. ** [http://sofacoustics.org/data/database/cipic cipic] HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/mit mit] HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** [http://sofacoustics.org/data/database/tu-berlin tu-berlin] HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances. ** [http://sofacoustics.org/data/database/oldenburg oldenburg] '''DRIRs''' from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. ** [http://sofacoustics.org/data/database/fhk fhk] '''HRTFs''' from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. High spatial resolution provided. * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs ce4718102e762b68b308a19e09e3d2ce89b9bc95 1707 1704 2013-11-27T21:13:32Z Petibub 4 SCUT added wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The following data are available at the moment: * [http://sofacoustics.org/data/database database] (HRTFs for general purposes]) ** [http://sofacoustics.org/data/database/listen LISTEN] HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/ari ARI] HRTF from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** [http://sofacoustics.org/data/database/ari_bte ARI_bte] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. Behind-the-ear HRTFs and DTFs. ** [http://sofacoustics.org/data/database/cipic CIPIC] HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/mit MIT] HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** [http://sofacoustics.org/data/database/tu-berlin TU-Berlin] HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ** [http://sofacoustics.org/data/database/oldenburg Oldenburg] '''DRIRs''' from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. ** [http://sofacoustics.org/data/database/fhk FHK] HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. High spatial resolution provided. ** [http://sofacoustics.org/data/database/scut SCUT] Near-field HRTFs from SCUT (Bosun Xie, China) of the KEMAR (Radius: 0.2 to 1.0 m). * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs 1e056a90815dfa0262dff3c781ab9169865eb7f1 1715 1707 2014-03-20T17:33:32Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The following data are available at the moment: * [http://sofacoustics.org/data/database database] (HRTFs for general purposes]) ** [http://sofacoustics.org/data/database/listen LISTEN] HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/ari ARI] HRTF from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. '''Currently not available, upgrading to SOFA 0.6''' ** [http://sofacoustics.org/data/database/ari_bte ARI_bte] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. Behind-the-ear HRTFs and DTFs. '''Currently not available, upgrading to SOFA 0.6''' ** [http://sofacoustics.org/data/database/cipic CIPIC] HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/mit MIT] HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** [http://sofacoustics.org/data/database/tu-berlin TU-Berlin] HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ** [http://sofacoustics.org/data/database/oldenburg Oldenburg] '''DRIRs''' from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. ** [http://sofacoustics.org/data/database/fhk FHK] HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. High spatial resolution provided. ** [http://sofacoustics.org/data/database/scut SCUT] Near-field HRTFs from SCUT (Bosun Xie, China) of the KEMAR (Radius: 0.2 to 1.0 m). * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs 9b7d96224f7d2ca78151b8769159777b8d689d25 1717 1715 2014-03-21T12:21:43Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The main SOFA repository http://sofacoustics.org/data is just in the process of being created. Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). The data can be, however, downloaded as they are. The following data are available at the moment: * [http://sofacoustics.org/data/database database] (HRTFs for general purposes]) ** [http://sofacoustics.org/data/database/listen LISTEN] HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/ari ARI] HRTF from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. '''Currently not available, upgrading to SOFA 0.6''' ** [http://sofacoustics.org/data/database/ari_bte ARI_bte] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. Behind-the-ear HRTFs and DTFs. '''Currently not available, upgrading to SOFA 0.6''' ** [http://sofacoustics.org/data/database/cipic CIPIC] HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/mit MIT] HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** [http://sofacoustics.org/data/database/tu-berlin TU-Berlin] HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ** [http://sofacoustics.org/data/database/oldenburg Oldenburg] '''DRIRs''' from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. ** [http://sofacoustics.org/data/database/fhk FHK] HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ** [http://sofacoustics.org/data/database/scut SCUT] Near-field HRTFs from SCUT (Bosun Xie, China) of the KEMAR (Radius: 0.2 to 1.0 m). ** [http://sofacoustics.org/data/database/riec RIEC] HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database (Kanji Watanabe, Japan) of many human listeners. * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs 27cecd10f76f329338afce5db59fe87847764a77 1718 1717 2014-03-25T12:50:51Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are. The following data are available at the moment: General purpose [http://sofacoustics.org/data/database database]: * HRTFs: ** [http://sofacoustics.org/data/database/ari ARI] HRTF from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ''Currently not available, upgrading to SOFA 0.6'' ** [http://sofacoustics.org/data/database/ari_bte ARI_bte] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. Behind-the-ear HRTFs and DTFs. ''Currently not available, upgrading to SOFA 0.6'' ** [http://sofacoustics.org/data/database/cipic CIPIC] HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/listen LISTEN] HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/mit MIT] HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** [http://sofacoustics.org/data/database/fhk FHK] HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' ** '''New: [http://sofacoustics.org/data/database/riec RIEC] Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''' ''(Credit: Kajni Watanabe, Japan)'' ** [http://sofacoustics.org/data/database/scut SCUT] Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' ** [http://sofacoustics.org/data/database/tu-berlin TU-Berlin] HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * DRIRs: ** [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. Special purpose: * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html e3922ae8a58000ae73c2c926ed500338aff34045 1722 1718 2014-04-08T07:27:07Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are. The following data are available at the moment: General purpose [http://sofacoustics.org/data/database database]: * HRTFs: ** [http://sofacoustics.org/data/database/ari ARI] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. '''New files with low-frequency content for hi-fi listening experience: "HRTF B" and "DTF B".''' ** [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. Behind-the-ear HRTFs and DTFs. ** [http://sofacoustics.org/data/database/cipic CIPIC] HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/listen LISTEN] HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/mit MIT] HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** [http://sofacoustics.org/data/database/fhk FHK] HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' ** '''New: [http://sofacoustics.org/data/database/riec RIEC] Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''' ''(Credit: Kajni Watanabe, Japan)'' ** [http://sofacoustics.org/data/database/scut SCUT] Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' ** [http://sofacoustics.org/data/database/tu-berlin TU-Berlin] HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * DRIRs: ** [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. Special purpose: * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html d24ea8a2d9d64efe2a29396f56c99875fdcfdd55 1723 1722 2014-05-20T16:24:59Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are. The following data are available at the moment: General purpose [http://sofacoustics.org/data/database database]: * Standard (in-the-ear canal) HRTFs of humans: ** [http://sofacoustics.org/data/database/ari ARI] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. '''New files with low-frequency content for hi-fi listening experience: "HRTF B" and "DTF B".''' ** [http://sofacoustics.org/data/database/cipic CIPIC] HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/listen LISTEN] HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** '''New: [http://sofacoustics.org/data/database/riec RIEC] Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''' ''(Credit: Kajni Watanabe, Japan)'' * HRTFs of artificial heads: ** [http://sofacoustics.org/data/database/mit MIT] HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** [http://sofacoustics.org/data/database/fhk FHK] HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' ** [http://sofacoustics.org/data/database/scut SCUT] Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' ** [http://sofacoustics.org/data/database/tu-berlin TU-Berlin] HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * Special HRTFs: ** [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)] HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. Behind-the-ear HRTFs and DTFs. * DRIRs: ** [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. Special purpose: * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 2aaf3caf0c74a50ea5a6263f6c65981d04e47481 1724 1723 2014-05-23T14:55:12Z Petibub 4 ARI (ARTIFICIAL) added wikitext text/x-wiki == Main SOFA repository == The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. General purpose [http://sofacoustics.org/data/database database]: * Standard (in-the-ear canal) HRTFs of humans: ** [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. *** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz *** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ** [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. ** [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/listen LISTEN]: HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * HRTFs of artificial heads: ** [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** '''New: [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ''' *** NH169: HRTFs, DTFs, and raw data of a printed head of an actual human listener *** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. ** [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' ** [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' ** [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * Special HRTFs: ** [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. * DRIRs: ** [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. Special purpose: * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html d2a3d47c1187a5acffbc6e83c516075ff8c205ac 1725 1724 2014-06-10T12:35:59Z Petibub 4 wikitext text/x-wiki == Main SOFA repository == The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. General purpose [http://sofacoustics.org/data/database database]: * Standard (in-the-ear canal) HRTFs of humans: ** [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. *** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz *** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ** [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. ** [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. ** [http://sofacoustics.org/data/database/listen LISTEN]: HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. ** [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * HRTFs of artificial heads: ** [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. ** '''New: [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ''' *** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener *** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. ** [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' ** [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' ** [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * Special HRTFs: ** [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. * DRIRs: ** [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. Special purpose: * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html fb7ec25b01eaa7439b7e45ca3f482d36bab09c5a 1726 1725 2014-06-10T12:38:57Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/listen LISTEN]: HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * '''New: [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ''' ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 6c37c488f79574c962a82010be42bff9f3c29d7b 0 14 1701 1642 2013-09-02T08:53:46Z Petibub 4 Reverted edits by [[Special:Contributions/31.184.238.68|31.184.238.68]] ([[User talk:31.184.238.68|talk]]) to last revision by [[User:Testente|Testente]] wikitext text/x-wiki == Common Data Form Language (CDL) == SOFA conventions can be implemented without any programming by using CDL as suggested for [http://en.wikipedia.org/wiki/NetCDF netCDF]. CDL files allow for a [http://en.wikipedia.org/wiki/Cross-platform platform-independent] interpretation of specifications and can be compiled to a binary [http://en.wikipedia.org/wiki/NetCDF netCDF] file using the ncgen tool from the netCDF package: ncgen -b -o mySOFAfile.sofa -k3 mySOFAconvention.cdl The binaries of the nc-tools are available at the Unidata. == HDF5View == SOFA files can be loaded and edited in the [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] - a viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files. Note that SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4], which is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. ac46afdb4cc29c564c773b9ddb9493e3e0299313 1716 1701 2014-03-20T17:34:29Z Petibub 4 wikitext text/x-wiki == HDF5View == SOFA files can be loaded and edited in the [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] - a viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files. Note that SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4], which is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. 6c7010453c0b4e103e1eeb03e694026e85859ffb 0 1 1705 1683 2013-11-18T13:27:20Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. ''' New! High-spatial resolution HRTFs of Neumann K100 added ''' * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 88b72672e6ed55744a54abeab7b56788794bd668 1706 1705 2013-11-18T13:27:50Z Petibub 4 fhk added wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. ''' New: High-spatial resolution HRTFs of Neumann K100 added! ''' * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by a variety of software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 88df711e173b29334896c4a6fb013c69d1a0cead 1719 1706 2014-03-25T12:56:02Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: RIEC Far-field HRTFs from the RIEC database of over 100 human listeners added!''' * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 22efec5556d4840e465d2bc71a3e68cbeb33da40 1736 1719 2014-06-13T14:05:10Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: HRTFs of mannequins (dummy heads) measured using the same setup as for human listeners''' * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software]] * [[APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 0e50c92731f7ee76a8f0745c4635b334502cb966 0 16 1709 145 2014-03-16T20:50:14Z Petibub 4 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. Also you are invited to contact the standardization committee of X212. Join us at ([http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 248c8e89960fc1fe6fb2fefbd0f14089d1bca45a 1721 1709 2014-03-26T08:11:18Z Petibub 4 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): one of the project initiators, Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Matlab support, website support * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) * '''Yukio Iwaya''' (Faculty of Engineering, Tohoku Gakuin University) Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. Also you are invited to contact the standardization committee of X212. Join us at ([http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 7caa55870c1291b2af1b3842cb8054ad1cad55cc 4 460 1720 2014-03-25T12:57:39Z Petibub 4 Created page with "This website is hosted by the [http://www.kfs.oeaw.ac.at/ Acoustics Research Institute], a research institute of the [http://www.oeaw.ac.at/ Austrian Academy of Sciences]. Th..." wikitext text/x-wiki This website is hosted by the [http://www.kfs.oeaw.ac.at/ Acoustics Research Institute], a research institute of the [http://www.oeaw.ac.at/ Austrian Academy of Sciences]. This website is supported by the [http://fwf.ac.at/ Austrian Science Fund (FWF)]. 6ea68636f0b6348b86d79c153a0bb06cf815fbe0 1 461 1727 2014-06-13T13:36:29Z Petibub 4 Created page with "==Type of data== * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R..." wikitext text/x-wiki ==Type of data== * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * equalization: I found this term in our previous discussions, please comment on that ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? ==Other aspects discussed until now== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are: * Producer: * Model: * FormFactor: * EarcupDesign * Technology * FrequencyResponse * Sensitivity * t.b.n for Stimulus Type (???) These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. 252362266792c028c4d29844aa0dc3134a1a87e5 1728 1727 2014-06-13T13:37:03Z Petibub 4 /* Other aspects discussed until now */ wikitext text/x-wiki ==Type of data== * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * equalization: I found this term in our previous discussions, please comment on that ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are: * Producer: * Model: * FormFactor: * EarcupDesign * Technology * FrequencyResponse * Sensitivity * t.b.n for Stimulus Type (???) These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. 4d21415cf2e3786f8757d2559f7d30ce92f98dee 1729 1728 2014-06-13T13:40:04Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==Type of data== * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * equalization: I found this term in our previous discussions, please comment on that ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. * EarcupDesign: t.b.d. * Technology: t.b.d * FrequencyResponse: t.b.d. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. 23008d110e3a3f3361458d63cf19e256febbc606 1731 1729 2014-06-13T13:45:12Z Petibub 4 wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * equalization: I found this term in our previous discussions, please comment on that... It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. Please comment on that! ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. * EarcupDesign: t.b.d. * Technology: t.b.d * FrequencyResponse: t.b.d. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. 12abf56803ec6eb18ac4949408461a234bf5a501 1732 1731 2014-06-13T13:53:19Z Petibub 4 wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * equalization: I found this term in our previous discussions, please comment on that... It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is the headphone represented in HeadphoneIR? The headphones as the product is the Source object, the individual headphones' drivers are the Emitters * What is special on HeadphoneIR compare to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. * EarcupDesign: t.b.d. * Technology: t.b.d * FrequencyResponse: t.b.d. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. 3a738a45fc3fef76ab2825633dfb4761d6ed6eab 1733 1732 2014-06-13T13:53:56Z Petibub 4 /* General */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * Equalization: I found this term in our previous discussions, but I don't know how to deal with that - please help... It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is the headphone represented in HeadphoneIR? The headphones as the product is the Source object, the individual headphones' drivers are the Emitters * What is special on HeadphoneIR compare to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. * EarcupDesign: t.b.d. * Technology: t.b.d * FrequencyResponse: t.b.d. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. 966b733e23f89e07561d994691dc955c8fbe53a5 1734 1733 2014-06-13T13:54:57Z Petibub 4 wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * Equalization: I found this term in our previous discussions, but I don't know how to deal with that - please help... It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. * EarcupDesign: t.b.d. * Technology: t.b.d * FrequencyResponse: t.b.d. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. 23f7f53275b84f478c6a2206a087ab91449db821 1 461 1737 1734 2014-06-13T14:44:27Z Petibub 4 wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * Equalization: I found this term in our previous discussions, but I don't know how to deal with that - please help... It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. * EarcupDesign: t.b.d. * Technology: t.b.d * FrequencyResponse: t.b.d. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. 94079826e2605b9c90f15e304cf621671c991cb1 1742 1737 2014-06-23T13:07:36Z Fbrinkmann 748 wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw: I think that that's the "merged", is it? * Equalization: Maybe this means that frequency responses of recording microphones were equalized? * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. ** FBrinkmann: What do you mean by this? * EarcupDesign: t.b.d. * Technology: t.b.d ** FBrinkmann: What do you mean by this? * FrequencyResponse: t.b.d. ** FBrinkmann: IMHO not needed (see comment below) * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. c245bf9b46499bf27b0f8f40efade67083d6908b 1743 1742 2014-06-23T13:51:54Z Geronazzo.michele 756 /* General */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. ** FBrinkmann: What do you mean by this? * EarcupDesign: t.b.d. * Technology: t.b.d ** FBrinkmann: What do you mean by this? * FrequencyResponse: t.b.d. ** FBrinkmann: IMHO not needed (see comment below) * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. d923040b744bbe38ef516d178a2773e37f801526 1745 1743 2014-06-23T15:15:18Z Geronazzo.michele 756 /* Single subject vs multiple subjecs */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. ** FBrinkmann: What do you mean by this? * EarcupDesign: t.b.d. * Technology: t.b.d ** FBrinkmann: What do you mean by this? * FrequencyResponse: t.b.d. ** FBrinkmann: IMHO not needed (see comment below) * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ee51292d7cad65182aa9ed58bb54efa18284b3ad 1746 1745 2014-06-23T15:18:11Z Geronazzo.michele 756 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. ** FBrinkmann: What do you mean by this? * EarcupDesign: t.b.d. * Technology: t.b.d ** FBrinkmann: What do you mean by this? * FrequencyResponse: t.b.d. ** FBrinkmann: IMHO not needed (see comment below) * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. b0b3aa40eb19e8298682682c14b0d252d6784fa2 1747 1746 2014-06-24T07:00:58Z Geronazzo.michele 756 /* Handling of SOFA-obligatory data */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: * Model: t.b.d * FormFactor: t.b.d. ** FBrinkmann: What do you mean by this? * EarcupDesign: t.b.d. * Technology: t.b.d ** FBrinkmann: What do you mean by this? * FrequencyResponse: t.b.d. ** FBrinkmann: IMHO not needed (see comment below) * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. bb509b3f3c8c10be8086849262ab3ceb226f3c0f 1748 1747 2014-06-24T08:38:54Z Geronazzo.michele 756 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: manufacturer name * Model: item name from manufacturers * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. Just to be sure, could you tell me if SOFA API already has functions able to know that a “.sofa” file belongs to a HeadphoneIR convention? SOFA users should be able to automatically distinguish between typologies of Source without see their attributes. b116ca24fdd45ec06912360dcbd9fc82f279d37e 1749 1748 2014-07-06T09:57:17Z Geronazzo.michele 756 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: manufacturer name * Model: item name from manufacturers * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. 5a3e2f373971b3b32e995c0900830a92029c0e03 1750 1749 2014-07-07T22:55:04Z Petibub 4 /* Single subject vs multiple subjecs */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: manufacturer name * Model: item name from manufacturers * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. a0f4353bd1bd9e5eec4e8b9ad0c21aa3aa38f936 1751 1750 2014-07-07T22:59:43Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the ISO-8601 format "yyyy-mmdd HH:MM:SS". So the actual time will be provided anyway. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: manufacturer name * Model: item name from manufacturers * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. 9528b1cca1232b72480a6b63138909f6a8bf101f 1752 1751 2014-07-07T23:00:44Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the ISO-8601 format "yyyy-mmdd HH:MM:SS". So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: manufacturer name * Model: item name from manufacturers * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. bdb2f1607c47c23e86f0d8089349e9510b1ba430 1753 1752 2014-07-07T23:05:47Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: manufacturer name * Model: item name from manufacturers * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ee8ad87142bf5d068b3fb768057a742168d970d3 1754 1753 2014-07-07T23:20:33Z Petibub 4 /* Handling of SOFA-obligatory data */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: manufacturer name * Model: item name from manufacturers * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. efd1dadcf64ec9fb5105c1bcfde7b31cb0a1afdc 1755 1754 2014-07-07T23:21:18Z Petibub 4 /* Handling of SOFA-obligatory data */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * Producer: manufacturer name * Model: item name from manufacturers * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. These attributes should be defined, and also the ambiguity should be reduced. For example, what does "FrequencyResponse" tell when we store the IRs in the numeric way in the same file anyway. When we provide the same information twice, which overrides which? FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. c3674de973a8843f441f406ce87b52e5324b7225 1756 1755 2014-07-07T23:40:04Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. The attributes proposed so far are (t.b.d.: to be defined): * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed (see comment below) ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. * Sensitivity: t.b.d * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** PM: Agreed, attribute will not be considered. FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? PM: Please define Tracking and Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. PM: Agreed. We will use SourceXXX as much as possible. 32d536a35187487606bbf927ac8605385180eaea 1757 1756 2014-07-07T23:47:51Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 1e3b356153af3a06fb6c15bfb51ea174a9637f14 1758 1757 2014-07-07T23:59:47Z Petibub 4 /* General */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 400b20072b3819cd88913190f95229c75bd62584 1759 1758 2014-07-14T17:14:27Z Geronazzo.michele 756 /* General */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjecs== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. d645b198b11677acaea8c60a029ced9d0186d6ff 1760 1759 2014-07-14T17:40:29Z Geronazzo.michele 756 /* Single subject vs multiple subjecs */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. ** MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 6f83e0504d205570f73af1ab1993408192211f99 1761 1760 2014-07-14T17:54:40Z Geronazzo.michele 756 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: *** ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 4c2753054e8077967072afe6441ba602b63a74f1 1762 1761 2014-07-14T17:55:51Z Geronazzo.michele 756 /* Handling of SOFA-obligatory data */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: *** ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. * the stimulus type (e.g. sine sweep): t.b.d * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum * Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. d15b8968a323c701449013ff1a333c7da63b0b52 1763 1762 2014-07-14T17:59:17Z Geronazzo.michele 756 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: *** ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. ed868fdbd2bf0d770049550e066b6e3747686b76 1766 1763 2014-07-23T07:42:20Z Petibub 4 Petibub moved page [[Talk:HeadphoneIR]] to [[Talk:SimpleHeadphoneIR]] wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: *** ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. ed868fdbd2bf0d770049550e066b6e3747686b76 1775 1766 2014-07-23T08:25:06Z Petibub 4 /* Single subject vs multiple subjects */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: *** ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 78cf43bb6424312ca2ca21de15286061f91cbbad 1780 1775 2014-07-24T18:00:33Z Petibub 4 /* General */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: *** ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. fc16bcf3dc687c1153e0098738e6b9af7c205725 1781 1780 2014-07-24T18:01:29Z Petibub 4 /* Single subject vs multiple subjects */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: *** ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. a711a5f40462f395bcc11b196aac7cb3dc23bc51 1782 1781 2014-07-24T18:06:09Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? * PM2: Agreed. Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: *** ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition *** PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 099c59a90b5b2ab540943d48e08cfd02e59ebc5a 1783 1782 2014-07-24T18:06:39Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? * PM2: Agreed. Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d ** FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. ** MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. ** MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? ** PM: Please define Tracking. ** MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition ** PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 019136179e1d7a486e75de26646fb96e57d2e017 1784 1783 2014-07-24T18:07:01Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? * PM2: Agreed. Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. a2be6f2b9a246b0515202a555de28c1ca59228d4 1785 1784 2014-07-24T18:10:03Z Petibub 4 /* Handling of SOFA-obligatory data */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? * PM2: Agreed. Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use '''SimpleFreeFieldHRIR''' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 1763b2222c568a9e3bf1bd9ffe310015d75db7c5 1786 1785 2014-07-24T18:10:18Z Petibub 4 /* Handling of SOFA-obligatory data */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? * MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? * PM2: Agreed. Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 1adf60d165d9bcc711cbb5ba575777b8c570cde0 2 464 1738 2014-06-20T09:46:05Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki austria austria austria austria austria austria austria austria austria austria austria austria austria austria austria austria austria cf230f39598cb2ffedb2c31206a900f13daee773 3 465 1739 2014-06-20T09:46:05Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 11:46, 20 June 2014 (CEST) 6b94be45f70133bb3e397d5b4c7c3b9ebaaa1b67 2 466 1740 2014-06-20T09:57:22Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria Austria 2asddsa 97c86240e05db23c313269c8d6a289c06c446378 3 467 1741 2014-06-20T09:57:22Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 11:57, 20 June 2014 (CEST) 022d0ce13c76cf2e6055ebb8e215fc4e2cb21566 1 463 1744 1655 2014-06-23T14:46:15Z Isfmiho 3 spam deleted in discussion wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 459 1764 1735 2014-07-23T07:42:14Z Petibub 4 Petibub moved page [[HeadphoneIR]] to [[SimpleHeadphoneIR]] wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} dbd61117cdc4ab57fde6f042ae4f7644d343534a 1769 1764 2014-07-23T07:44:16Z Petibub 4 wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.2 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 7e3d3f8ca7dcb95b2a1992a4b3693161b0fcec31 1770 1769 2014-07-23T07:45:22Z Petibub 4 /* Proposed version 0.2 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} f333f02c39919c354f6eada128d1d1a1c699df75 1772 1770 2014-07-23T07:49:48Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 0b3bf36bc9db2bcad620af377e59986547e7d2a0 1773 1772 2014-07-23T08:18:23Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions SimpleHeadphoneIR we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of SimpleHeadphoneIR are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: E1-->R1,R2; next measurement: E2-->R1, R2. Usually, the IRs E1-->R1 and E2-->R2 are the interesting IRs and are usually further processed. This one-to-one correspondence of emitters and receivers is a strict property of SimpleHeadphoneIR. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, GeneralFIR is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. * '''Simple sources, simple listeners''': the orientation (View and Up variables) of the emitters and receivers are not considered. This makes the conventions simple, corresponding to the simplicity of SimpleFreeFieldHRIR. == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} dec4c66af03eaf18f9264d98c7412a669c91ae5c 1774 1773 2014-07-23T08:20:19Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions SimpleHeadphoneIR we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of SimpleHeadphoneIR are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is a strict property of SimpleHeadphoneIR. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, GeneralFIR is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. * '''Simple sources, simple listeners''': the orientation (View and Up variables) of the emitters and receivers are not considered. This makes the conventions simple, corresponding to the simplicity of SimpleFreeFieldHRIR. == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 8393386d441179a7b96ab7c50e5c3be0878c437d 1776 1774 2014-07-23T08:32:51Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. * '''Simple sources, simple listeners''': the orientation (View and Up variables) of the emitters and receivers are not considered. This makes the conventions simple, corresponding to the simplicity of ''SimpleFreeFieldHRIR''. Note that the orientation of the source (i.e., headphones) and the listener is considered in order to capture the repositions of the headphones in the measurements. In ''SimpleHeadphoneIR'', the various measurements correspond to repeated measurements of the same listener. The repetition can be done under various modifications: * No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. * Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. * The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 40eec8e85ed3c0a573fe46aa0c03cf181f2e37a5 1777 1776 2014-07-23T08:44:52Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SingleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. In ''SimpleHeadphoneIR'', the various measurements correspond to repeated measurements of the same listener. The repetition can be done under various modifications: * No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. * Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. * The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 355a6426529cb5423575d634a7d6ad0c4054a396 1778 1777 2014-07-23T08:45:03Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. In ''SimpleHeadphoneIR'', the various measurements correspond to repeated measurements of the same listener. The repetition can be done under various modifications: * No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. * Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. * The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} e26bd34ea900b68194170b07fc3a42d491039df3 1779 1778 2014-07-23T08:47:53Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 0c7a0aa2588ed08dcfe9f79bd6f1efb30eaec786 0 468 1765 2014-07-23T07:42:14Z Petibub 4 Petibub moved page [[HeadphoneIR]] to [[SimpleHeadphoneIR]] wikitext text/x-wiki #REDIRECT [[SimpleHeadphoneIR]] 93e3e98aeb0bb03a0e40fd8baefddbb2efedd42e 1 469 1767 2014-07-23T07:42:20Z Petibub 4 Petibub moved page [[Talk:HeadphoneIR]] to [[Talk:SimpleHeadphoneIR]] wikitext text/x-wiki #REDIRECT [[Talk:SimpleHeadphoneIR]] 6cf9c548ee995e5a72668f09d73fc737082ea567 0 5 1768 1708 2014-07-23T07:43:09Z Petibub 4 /* Proposed SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with TF as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with FIR as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 45695c540d666dbde9480fbac0bde1a37d272251 6 470 1771 2014-07-23T07:48:53Z Petibub 4 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1 461 1787 1786 2014-07-24T20:06:41Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceDescription (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 9fab87364d020c00971e36f8c6c8daaf744f9504 1788 1787 2014-07-24T20:24:57Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceDescription (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM2: I think that we should separate the description of acoustic data from building up a database of headphone specs. I'm afraid that including too much information on the specs in the SOFA files which actually should contain IRs only, might lead to an inconsistency. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could link to the particular specs file. For example, for the specs of Sennheiser HD 520 II we could store SourceDescription = 'http://www.manualslib.com/download/345497/Sennheiser-Hd-520-Ii.html'. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 61e17a56ebaedf93f9b9ce40dcdddec3f75b76fc 1789 1788 2014-07-24T20:25:16Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceDescription (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM2: I think that we should separate the description of acoustic data from building up a database of headphone specs. I'm afraid that including too much information on the specs in the SOFA files which actually should contain IRs only, might lead to an inconsistency. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could link to the particular specs file. For example, for the specs of Sennheiser HD 520 II we could store SourceDescription = 'http://www.manualslib.com/download/345497/Sennheiser-Hd-520-Ii.html '. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 4f25a6a5b7bc58579123c2df3be1824b80eebf95 1790 1789 2014-07-24T20:29:27Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceDescription (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM2: I think that we should separate the description of acoustic data from building up a database of headphone specs. I'm afraid that including too much information on the specs in the SOFA files which actually should contain IRs only, might lead to an inconsistency. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could link to the particular specs file. For example, for the specs of Sennheiser HD 520 II we could store SourceDescription = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 6ca631a8c74d6c7a31a50ec7ad64a39fbd829345 1791 1790 2014-07-24T20:38:59Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceDescription (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM2: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceDescription = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. What do you think? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. a1aa3b813f93ac67936bf450df832b38f07b8775 1792 1791 2014-07-24T20:41:40Z Petibub 4 /* Single subject vs multiple subjects */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceDescription (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM2: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceDescription = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. What do you think? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. e52a68094410bc757afbf4a26ea82ecebc4c65e9 1794 1792 2014-07-24T20:45:52Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM2: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceDescription = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. What do you think? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. d5839e04a9125eaf15174d8eb67b08857679e039 1795 1794 2014-07-24T20:46:12Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM2: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. What do you think? * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 2cd640f7fb65af19c7341570cdc959c24ee8d532 1798 1795 2014-07-24T20:54:31Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM2: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. f6416d3981dc5d128f519be65eaa8461a6275c0c 1799 1798 2014-07-24T20:59:19Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 69c1a81d75e6a735d147a8f76f6b86b545b69b46 1801 1799 2014-07-25T12:33:50Z Fbrinkmann 748 /* Single subject vs multiple subjects */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 8f501b11a1e32a0f8fae34cde4b8d166024af64a 1803 1801 2014-07-25T13:10:12Z Fbrinkmann 748 /* Handling of SOFA-obligatory data */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 5a66bf88d05b279609ca40e1c625d174b3e2220c 1804 1803 2014-07-25T13:21:21Z Fbrinkmann 748 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. FB: Agreed to PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 9fe1cc108ce57ed2dc39c18b9d8a3b4b7e7f9295 1805 1804 2014-07-25T13:24:33Z Fbrinkmann 748 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. FB: Agreed to PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 08ed4a9a295ca60648d8f588ec3ce9440a2155ba 1806 1805 2014-07-29T20:33:46Z Petibub 4 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. FB: Agreed to PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. a6f222b5e563239fb92d2efe75b92b78d7b9d1dc 1807 1806 2014-07-29T20:35:36Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. FB: Agreed to PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. c8f461dffb5218099a30a9a6a63c6f0211875392 1808 1807 2014-07-30T12:19:29Z Fbrinkmann 748 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. FB: Agreed to PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 8cdfca28b8a5d6476530ae53831d9f93cbe168e0 1809 1808 2014-08-06T16:24:32Z Bbboren 852 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. FB: Agreed to PM3. [[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 87870ce846263fd9c4e905ffcb7e76cd34d3ff7b 1810 1809 2014-08-06T16:28:35Z Bbboren 852 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. *FB: Agreed to PM3. *[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. **[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:28, 6 August 2014 (CEST) Also if you're using sine-sweeps and want to store the harmonic distortion products along with the impulse response, it would be useful to know the type of signal. But maybe that's not a common enough occurrence to worry about for these purposes. * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 3f1b81006b3e55b51fc49264f4a0a23206872a74 1811 1810 2014-08-11T09:50:05Z Petibub 4 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. *FB: Agreed to PM3. *[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. **[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:28, 6 August 2014 (CEST) Also if you're using sine-sweeps and want to store the harmonic distortion products along with the impulse response, it would be useful to know the type of signal. But maybe that's not a common enough occurrence to worry about for these purposes. ** PM3: I agree with Bbboren. For storing data other than IRs, I suggest to create an other datatype which would be able to store freqency-sweep responses. Then, we could create conventions which use that datatype for headphones (or maybe even for any kind of electro-acoustic device). For SimpleHeadphoneIR, I suggest to stick to IR. Agreed? * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. ded14b1f14288b84b341e4393d02b404d248a8a1 1819 1811 2014-08-25T21:32:14Z Geronazzo.michele 756 /* General */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. ** MG3: Absolutely agreed. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Single subject vs multiple subjects== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. *FB: Agreed to PM3. *[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. **[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:28, 6 August 2014 (CEST) Also if you're using sine-sweeps and want to store the harmonic distortion products along with the impulse response, it would be useful to know the type of signal. But maybe that's not a common enough occurrence to worry about for these purposes. ** PM3: I agree with Bbboren. For storing data other than IRs, I suggest to create an other datatype which would be able to store freqency-sweep responses. Then, we could create conventions which use that datatype for headphones (or maybe even for any kind of electro-acoustic device). For SimpleHeadphoneIR, I suggest to stick to IR. Agreed? * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 06029a199cea05603ecbcee32d345bd327f78138 1820 1819 2014-08-25T21:45:15Z Geronazzo.michele 756 /* Single subject vs multiple subjects */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. ** MG3: Absolutely agreed. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Subject/Headphone correspondences== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree MG3: Now, with string-array support, things become easier. Agreed. Moreover, we can define "one headphones --> many subjects" with different ListenerShortName and ListenerDescriptions (not GLOBAL:). What do you think about it? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. *FB: Agreed to PM3. *[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. **[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:28, 6 August 2014 (CEST) Also if you're using sine-sweeps and want to store the harmonic distortion products along with the impulse response, it would be useful to know the type of signal. But maybe that's not a common enough occurrence to worry about for these purposes. ** PM3: I agree with Bbboren. For storing data other than IRs, I suggest to create an other datatype which would be able to store freqency-sweep responses. Then, we could create conventions which use that datatype for headphones (or maybe even for any kind of electro-acoustic device). For SimpleHeadphoneIR, I suggest to stick to IR. Agreed? * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. f7cd1e43208351283113ccba794db55eef61283a 1821 1820 2014-08-25T21:46:23Z Geronazzo.michele 756 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. ** MG3: Absolutely agreed. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Subject/Headphone correspondences== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree MG3: Now, with string-array support, things become easier. Agreed. Moreover, we can define "one headphones --> many subjects" with different ListenerShortName and ListenerDescriptions (not GLOBAL:). What do you think about it? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 ** MG3: Agreed Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? • MG3: Agree with PM2 ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. *FB: Agreed to PM3. *[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. **[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:28, 6 August 2014 (CEST) Also if you're using sine-sweeps and want to store the harmonic distortion products along with the impulse response, it would be useful to know the type of signal. But maybe that's not a common enough occurrence to worry about for these purposes. ** PM3: I agree with Bbboren. For storing data other than IRs, I suggest to create an other datatype which would be able to store freqency-sweep responses. Then, we could create conventions which use that datatype for headphones (or maybe even for any kind of electro-acoustic device). For SimpleHeadphoneIR, I suggest to stick to IR. Agreed? * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 7eadec10fa08a6061fda61f5656d1177e0ad6323 1822 1821 2014-08-25T22:10:32Z Geronazzo.michele 756 /* Measurement repetition */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. ** MG3: Absolutely agreed. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Subject/Headphone correspondences== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree MG3: Now, with string-array support, things become easier. Agreed. Moreover, we can define "one headphones --> many subjects" with different ListenerShortName and ListenerDescriptions (not GLOBAL:). What do you think about it? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 ** MG3: Agreed Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? * MG3: Agree with PM2 ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. *FB: Agreed to PM3. *[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. **[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:28, 6 August 2014 (CEST) Also if you're using sine-sweeps and want to store the harmonic distortion products along with the impulse response, it would be useful to know the type of signal. But maybe that's not a common enough occurrence to worry about for these purposes. ** PM3: I agree with Bbboren. For storing data other than IRs, I suggest to create an other datatype which would be able to store freqency-sweep responses. Then, we could create conventions which use that datatype for headphones (or maybe even for any kind of electro-acoustic device). For SimpleHeadphoneIR, I suggest to stick to IR. Agreed? * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. 30fdff205c80640058b7b8a59dae132cd320dd1e 1823 1822 2014-08-25T22:14:20Z Geronazzo.michele 756 /* Handling of SOFA-obligatory data */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. ** MG3: Absolutely agreed. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Subject/Headphone correspondences== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree MG3: Now, with string-array support, things become easier. Agreed. Moreover, we can define "one headphones --> many subjects" with different ListenerShortName and ListenerDescriptions (not GLOBAL:). What do you think about it? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 ** MG3: Agreed Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? * MG3: Agree with PM2 ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. MG3: Perfect, olè! ;) Just to finish this section, uff… the joint usage of HpIR+HRIR (such QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat) has not to be encouraged, agree with me? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. *FB: Agreed to PM3. *[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. **[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:28, 6 August 2014 (CEST) Also if you're using sine-sweeps and want to store the harmonic distortion products along with the impulse response, it would be useful to know the type of signal. But maybe that's not a common enough occurrence to worry about for these purposes. ** PM3: I agree with Bbboren. For storing data other than IRs, I suggest to create an other datatype which would be able to store freqency-sweep responses. Then, we could create conventions which use that datatype for headphones (or maybe even for any kind of electro-acoustic device). For SimpleHeadphoneIR, I suggest to stick to IR. Agreed? * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. cc2790e3446eee93d3d03e5beaa1ac5f42ac36eb 1824 1823 2014-08-25T22:18:41Z Geronazzo.michele 756 /* Headphone related attributes */ wikitext text/x-wiki ==General== We actually want to store headphone IRs. Here is the summary of the discussion until now about the general way how can we represent measurements with headphones in SOFA: * Unmerged: When measuring headphones, we have two headphones (=two transmitters, T1 and T2) and we have two mics places in the ears (=two receivers, R1 and R2). For the first measurement: T1-->R1,R2; next measurement: T2-->R1, R2. So, the IRs T1-->R1 and T2-->R2 are the interesting ones and are usually further processed. But we also have the uninteresting IRs T1-->R2 and T2-->R1. They represent the cross-talk data, which we actually do not use, but we store them! And we could use SOFA for storing them. This could be covered by the conventions ''GeneralFIR''. * Merged: Now, for any further processing purposes, we are usually interested just in two IRs: #1: T1 --> R1 and #2: T2 --> R2. Thus, the number of receivers (here: 2) defines the number of IRs and transmitters, with a strict one-to-one correspondence between transmitters and receivers. I think that this could be the main property of ''HeadphoneIR'': a strict one-to-one correspondence between transmitters and receivers. * Raw and compensated IRs (Merged) : they share the same representation, except the information used to obtain the compensated signals from the raw ones. **Raw: data from the recordings. **Compensated: inverse filtering of the stimulus plus free-field/diffuse-field compensation in order to extrapolate the impulse response. It can be approximately seen as DTFs from HRTFs. * Equalization: we can think of storing equalization filters for different techniques. For a specific headphone model, we could have these equalization filters: **a one-to-one correspondence between transmitters and receivers (e.g. single measurement equalization) **a one-to-all repetitions for a specific subject (e.g. mean equalization) **a one-to-all repetitions for all the available subjects and, in the further development, grouping similar headphones (e.g. machine learning approach) * Inverted: In most cases, the merged HeadphoneIR data is used to design a headphone filter by inverting the HeadphoneIRs. This filter is then used for equalizing (cancelling out) the transfer function of the headphone during auralization. It might be good to store the inverted HeadphoneIRs because (a) the inversion itself is not trivial and others could use the filters without having to think about the proccesing, (b) documentation of an inversion method in conjunction with Matlab/C/Java-code -> reproducable research. There are two possibilities in dealing with the inverted IRs (a) storing merged and inverted Data in the same SOFA object and (b) storing them in separate objects. (a) might be difficult to handle because there usually is only one headphone filter altough there might be many HeadphoneIRs. Both, merged and inverted IRs could be saved in Data.IR and meta data could be used to tell what IR is inverted. This, however might be confusing. (b) can be achieved by matching subject IDs and description across objects holding merged and inverted data, wich can easily be done. ** PM: It seems to me like the "inverted HpIR" is not a HpIR but a filter used for filtering sounds. So, I suggest to not use SingleHeadphoneIR for storing filters. Instead I suggest 1) for the moment to use GeneralFIR and 2) later define new conventions which clearly state what is special on that filters. ** MG2: I agree with you. The better solution should be b) a new convention. Moreover, I feel that this convention is tightly connected with what we called: ''equalization filters for a one-to-one correspondence between transmitters and receivers''. Am I correct? Thus I suggest for the future something similar to ''EqSingleHedphoneFIR''. ** PM2: I understand MG2. My suggestion: Let's define the headphones conventions and then discuss the difference between the equ IRs and the HpIRs. ** MG3: Absolutely agreed. At the moment, the simple case is to have one-to-one correspondence. We could work on that first, and then think about multiple subjects in a file for both measured, inverted and equalized filters. We would need a clear and consistent definition for HeadphoneIR first. It seems like the one-to-one correspondence is the major property which clearly defines our HeadphoneIR conventions. So, this is how I see HeadphonesIR: * How is a headphone represented in HeadphoneIR? The headphones as the product is represented by the Source, the individual headphones' drivers are represented by the Emitters. * What is special on HeadphoneIR compared to, say, GeneralFIR? It is the one-to-one correspondence between the Emitters and the Receivers. For other issues, see the following sections. ==Subject/Headphone correspondences== At the moment, all SOFA files are for a single subject, i.e., one subject --> one file. For HpIRs, it makes sense to have a file containing data from several subjects, i.e., many subjects --> one file. What do you think? How would you like to deal with that issue? FBrinkmann: Note that the above mentioned case is the most common, but there might also be the case that we want to save HeadphoneIRs for one subject but different types of headphones (For example when trying to find headphone filters best matching a set of different headphone types). MG: Fabian’s observation sounds very desirable. Following his suggestion, the focus moves from headphones to subjects/group of headphones which is fine for me but conceptually merits a different convention. Let’s call it something similar to ''GroupHeaphoneIR''. PM: Agreed: then, we should call these conventions ''SingleHeadphoneIR''. MG2: further steps… (a rough sketch) ''MultipleHeadphoneIR'': one headphones --> many subjects ''GroupHeaphoneIR'': one subject --> many headphones PM2: one subject --> many headphones is equivalent to one subject --> repeated measurements of any headphones. Thus, I suggest to consider this case as measurement repetition. I further propose to change the name to ''SimpleHeadphoneIR'', because ''Single'' is ambiguous (it is not clear to what single refers to: subject or measurement, and it implies single headphones, which is definitely not the case). But we have conventions ''SimpleFreeFieldHRIR'' which also always consider a single subject and repeated measurements. Thus ''SimpleHeadphoneIR'' directly corresponds to ''SimpleFreeFieldHRIR''. I already created a short description on the main page. I hope that you agree... FB: agree MG3: Now, with string-array support, things become easier. Agreed. Moreover, we can define "one headphones --> many subjects" with different ListenerShortName and ListenerDescriptions (not GLOBAL:). What do you think about it? ==Measurement repetition== Usually, when a measurement is repeated, something in the measurement setup changes. For example, for HRTF measurements, we change the direction of the source and repeat the measurement. In the SOFA file, this is noted as a different entry in SourcePosition. Now, for HpIR, we have multiple measurements, which are just repetitions, i.e., the subjects put the HP on, we measure, the subjects takes the HP down, put it on again, we re-measure, and so on. What changes it the time, and the counter of the performed measurement. Neither the subject changes nor the Source, Emitter, Listener, Receiver attributes. My question: *do you also have this issue? How do you deal with that? How would you like to consider that in SOFA conventions? **FBrinkmann: At the moment we store our IRs as separate wav/mat files with consecutive numbering - wich is not an option for SOFA. **MG: I’ve suggested so far to store repetition on Obj.Data.IR = NaN(M,R,N); M repetitions, R channels and N samples. ** PM: Agreed. *At the moment, I suggest to have a variable called MeasurementTimeCreated in which, for each measurement, the date/time of the corresponding measurement would be stored. **FBrinkmann: I would suggest to save identical MeasurementTime Created for HeadphoneIRs measured on the same day and subject. This makes the data look somehow simpler, and I don't see a large advantage in saving exact times for each IR. **MG: Practically speaking, I agree with Fabian but we lose generality. One subject could perform several recording sessions made in different days and years. Subjects change their ear shape over time providing different acoustic contribution to HpIRs. **PM: MeasurementDate (sorry, it's called Date, not Time, my mistake) save the date and the time using the number of seconds from 1970-01-01 00:00:00. So the actual time will be provided anyway. If you agree, we define MeasurementDate to be optional. **MG2: Agreed. One can manage timestamps as he/she prefers. *Further, a variable called MeasurementDescription, in which, for each measurement, a string containing description of the corresponding measurement, would be stored. Note that we'd need string arrays in such a case, a feature currently not implemented in the Matlab API. **FBrinkmann: I think MeasurementDescription is already covered by the GLOBAL variables suggested in the HeadphoneIR convention version 0.1 - or do I miss something? In most cases it might be sufficient to specify these meta data entries once because the setup usually does not change. In this case we won't need string arrays. However having string arrays available (without knowing about the amount of work this would take) would make things way more flexible. This would for example make it possible to save IRs for one subject but different types of headphones. **MG: the use of several MeasurementDescription leads to a huge amount of redundant data because the setup usually does not change, as Fabian said. Different consideration should be noted with the case of single subject and different headphones which produces my comment on section ''single subject vs. multiple subject'' ** PM: guys, so what I don't understand then, is the following: we'll have many measurements in the file, but we do not provide any information (but the MeasurementDate) about what is different in the measurements? How do I know distinguish between the measurements then? ** MG2: I’ve got the point! What actually changes among measurements (with same setup) is the emitter positions. Following this observation we might move here at repetition-level the discussion on Tracking. Do you agree with me? ** PM2: Agreed. So, which attributes would you like to have as global attributes, i.e., one entry per file; and which as measurement-specific attributes, i.e., for each measurement a separate entry? ** FB2: I understand your point, but I don't see how we can determine the exact EmitterPosition as it is defined now (with respect to the ListenerPosition = interaural center) and I did not find a solution to this in the Tracking section. I would have two practical workarounds to this: either add some random numbers to the (assumed) emitter position [0 -0.09 0; 0 0.09 0] (not elegant?), or further specification in GLOBAL:comment : singe subject, single/multiple headphone/s with/without repositioning. ** PM3: It's not a problem. If you don't know the exact position of Emitters, just leave it at default. When repeating the measurement, the time will only change. In the comments, you still can describe if and how the repositioning was done. Agreed? ** FB3: Agree to PM3 ** MG3: Agreed Measurement-specific attributes: * MeasurementDate (measurement has been just repeated) * EmitterPosition (headphones have been repositioned) * SourceManufacturer (headphones changed) * SourceModel (headphones changed) * SourceURI (headphones changed) Tracking: tracking headphones position, once put on, is a challenging issue, but sometimes it's possible to give a label to the each repositionament e.g. simple labels: comfortable, not comfortable. t.b.d * FBrinkmann: It might be hard to establish comparability of the suggested labels (comfortable, not comfortable...) across subjects and research institutes (what does comfortable mean, where does not comfortable start?). Moreover, I'm not sure about the relevance of these labels: What does it tell us about the IR if the position was comfortable (I think most headphones available are comfortable to wear)? In my opinion the goodness of the headphone position is best reflected by the repeatability: Good positioning means little variance across repeated measurements of the same subject. I thus tend to dismiss this attribute. * MG: In principle, I agree. Simple labels have been proposed due to the challenging issue, i.e. tracking headphones position. But of course, the quantitative data could be stored in EmitterPosition. * MG: The latter comment seems to be misleading after reading the one related to Tracking headphones position. Could you clarify your opinion on that? * PM: Please define Tracking. * MG2: I try to propose a new repetition-level attribute related to Tracking which should be quantitative and optional, of course: ''DeltaEmitterPosition'': spatial deviation from the global EmitterPosition * PM2: another level of spatial relation is not defined in SOFA (EmitterPosition is already in the local coordinates of SourcePosition). But that's not a problem: The mechanism you would like to see is already considered by allowing to vary EmitterPosition for each M. Agreed? * MG3: Agree with PM2 ==Handling of SOFA-obligatory data== * SourcePosition: ** Suggestion 1: a fictive sound source position (example given: 0.5 m in front of the listener). The definition of the virtual position is unclear yet. The choice for the distance needs to be defined. ** Suggestion 2: the actual position of the headphones, usually congruent with ListenerPosition ***FBrinkmann: I prefer 2 ***PM: Agreed. * EmitterPosition: ** Suggestion 1: the actual position of the headphone drivers, according to SOFA rules must be relative to the SourcePosition. *** FBrinkmann: I agree. I think this is already included in the conventions 0.1 draft -> EmitterPosition = [0 -0.09 0; 0 0.09 0] *** PM: Agreed on your agreement :-). MG: Let's consider the case of QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat HRTFs from TU-Berlin; SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener, i.e. SourcePosition = [0 0 0.5]. Following the latter observation plus ListenerPosition=SourcePosition=[0 0 0] (always in the current convention), it's hard to describe EmitterPosition related to SourcePosition. I propose to anchor both Receiver- and Emitter- Position to ListenerPosition and use SourcePosition for the description of fictive sound sources. Summarizing my observation: * ListenerPosition = [0 0 0]; * SourcePosition = [0 0 0]; (no dimensions) / SourcePosition = [x y z]; (virtual sources) * ReceiverPosition = [0 -0.09 0; 0 0.09 0]; * EmitterPosition = [0 -0.09 0; 0 0.09 0]; What do you think about it? PM: I don't understand the statement "SourcePosition can be also seen as virtual position, e.g. previously measured without headphones at 0.5 m away from the listener". When measured without headphones, then we measure HRTFs, not HpIRs, right? So, at the moment, I agree with Fabian and vote for providing the actual positions of the headphones and the listener. But maybe I just did not understand the concept of "virtual position" - try to explain, please. In the meantime, I go for the actual positions... MG2: What I would like to define with ''virtual position'' is the follow scenario: one can employ HRTFs as stimuli, e.g. the QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat. I usually perform the convolution between HpIR and HRIR, separately, but my main concern regards the loss of generality of SingleHeadphoneIR convention. Another issue that is currently coming into my mind, just to be clarified: what happens if the actual SourcePosition is coming from a loudspeaker and the listener is wearing headphones? We should consider a specific setup for a SimpleFreeFieldHRIR, shouldn’t we? PM2: An HRTF measurement with wearing headphones is similar to an HRTF measurement with wearing a hut :-). Thus, these data will have the same format as those from an usual HRTF measurement and I suggest to use ''SimpleFreeFieldHRIR'' to store them. Also, ListenerDescription should contain something like "Listener was sitting in the center of the loudspeaker arc, was wearing the headphones XXXX and a sombrero.". Agreed? FB2: Agreed to PM2. MG3: Perfect, olè! ;) Just to finish this section, uff… the joint usage of HpIR+HRIR (such QU_KEMAR_anechoic_SennheiserHD25_0.5m.mat) has not to be encouraged, agree with me? == Headphone related attributes == The naming of the headphone related attributes needs to be clarified. In general, all attributes considering the headphones have the prefix Source. The attributes on which we agreed so far are: * SourceManufacturer: manufacturer name, optional. * SourceModel: model name from manufacturers, optional. The attributes proposed and currently being under discussion so far are (t.b.d.: to be defined): * FormFactor: Circumaural, Supra-aural, Earphones, etc. ''(MG: see my comment at the end of this list)''. ** FBrinkmann: What do you mean by this? ** PM: I think that this is redundant information as already given by the SourceModel. What do you think? * EarcupDesign: Closed, Open, etc. ''(MG: see my comment at the end of this list)''. * Technology: Transducer technology, e.g. Dynamic ''(MG: see my comment at the end of this list)'' ** FBrinkmann: What do you mean by this? * Sensitivity: t.b.d ** FBrinkmann: I find the attributes suggested in the draft 0.1 to be very reasonable already, and would suggest to use them and maybe add Sensitivity and Tracking of headphone position ** PM: Please define Sensitivity. ** PM2: I see that in our AES proceedings, the sensitivity was defined as "electroacoustic transducer sensitivity (transfer factor) in mV/Pa". Can you tell me, if this is a value which is supposed to be measured or is this just the value from the specs given by the manufacturer? MG: New attributes (w.r.t version 0.1) want to facilitate the relationship between product design attributes and acoustic responses of headphones. I feel that headphone characteristics (e.g. form factor, ear-cup design, etc.) have to be considered like the anthropometry for HRIRs. We should follow some standards in order to define these labels. Have you any strong feelings on this issue? PM: If you think that you need those attributes: OK, no problem. Please define them, particularly paying attention to avoid redundancy (information provided already by the SourceModel). MG2: All these attributes are somehow redundant once SourceModel is considered with an available product sheet. But anyway, we have to answer to the following question: why might it be important to perform a meta-analysis on model characteristics? PM3: With manufacturer and model, a meta analysis can be performed by using the headphone specs provided by the manufacturer. I'm afraid that including too much information on the headphone specs in the SOFA files (which actually should contain IRs only) will lead to an inconsistency. Further, attributes like EarCup or FormFactor must be optional, because we cannot ensure that everybody will have these data or know what would be the appropriate values. By storing the manufacturer and the type in the SOFA file, the link to the corresponding specs will be unique anyway. So providing more information than manufacturer/model does not help. I thus suggest to store specs and IRs in separate files. If you think that it is not clear what specs are describing the measured headphones, we could provide a link to the particular specs file. For example, for the specs of Sennheiser HD 520 II, we could store SourceURI = 'http://mypdfmanuals.com/user-manual,SENNHEISER,HD%2B520+II,3708267.pdf '. This way, we would avoid inconsistencies because the meta data would always correspond to those given by the manufacturer. And, in the case of having specs which differ from the manufacturer specs, one could provide a link to a custom-made specs file. Note that you still can provide more attributes, however, they don't have to be defined in conventions. *FB: Agreed to PM3. *[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:24, 6 August 2014 (CEST): Agreed re:PM3. * MG3: smart choice, agreed. I’ve noticed that in the proposed SimpleHeadphoneIR there isn't SourceURI at measurement level, but only GLOBAL:SourceURI. * the stimulus type (e.g. sine sweep): t.b.d ** MG2: This attribute is useless if we consider the IR. But, if I want to store raw data, i.e. recordings without processing, we need to specify the stimulus type, e.g. a sine sweep response. How have you handled this issue in the SimpleFreeFieldHRIR convention? I’m probably missing something here... ** PM2: In SimpleFreeFieldHRIR, we store impulse responses. **[[User:Bbboren|Bbboren]] ([[User talk:Bbboren|talk]]) 18:28, 6 August 2014 (CEST) Also if you're using sine-sweeps and want to store the harmonic distortion products along with the impulse response, it would be useful to know the type of signal. But maybe that's not a common enough occurrence to worry about for these purposes. ** PM3: I agree with Bbboren. For storing data other than IRs, I suggest to create an other datatype which would be able to store freqency-sweep responses. Then, we could create conventions which use that datatype for headphones (or maybe even for any kind of electro-acoustic device). For SimpleHeadphoneIR, I suggest to stick to IR. Agreed? ** MG3: Agreed. Furthermore, just to have a clear view of the naming philosophy, you are going to call such conventions without “IR” suffix, correct? * qualitative data about microphone/receiver position, e.g. blocked ear canal, open ear canal, at the eardrum ** MG2: Optional (when tracking data are not available). ** Because such an information is not clearly defined yet, in SimpleFreeFieldHRIR, we use the attribute Comments for storing that information. I suggest to use that information for the headphones as well. ** FB: I think this should be stored in GLOBAL:ReceiverDescription rather than in GLOBAL:Comments, and could provide any information found to be useful (eg. simple specification as microphone type, or publication etc.) ** PM: Agreed to FB. ReceiverDescription seems to be the perfect place. MG: do you agree? ** MG3: Agreed with both of you. ---- The attributes which as the result of our discussion, won't be considered are so far: * FrequencyResponse: declared (from the manufacturer) frequency range, e.g. 12-20000 Hz ** FBrinkmann: IMHO not needed ** MG: I agree that this is not mandatory nor useful. ** PM: Agreed, attribute won't be considered. Further, the structure of the attributes should be defined as well: Candidates (with XXX being one of the above-stated attributes): * Headphones.XXX does not work because SOFA does not allow nested structures. * GLOBAL_HeadphonesXXX is allowed, but the difference to SourceXXX should be clearly defined then. * In SOFA, the headphones are represented by the object Source. Thus, we could use GLOBAL_SourceXXX. ** FBrinkmann: I am in favour of this. ** MG: I proposed GLOBAL_HeadphonesXXX in order to characterize this convention. Now, I realize that GLOBAL_SourceXXX should be the most adequate for headphones. SOFA API already has the field GLOBAL:SOFAConventions, thus users are able to know that a “.sofa” file belongs to a HeadphoneIR convention and to automatically distinguish between typologies of Source and characteristic attributes. ** PM: Agreed. We will use SourceXXX as much as possible. d224da235de0eec6d19cff39d8d812bb34f20d9b 0 459 1793 1779 2014-07-24T20:45:07Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. At the moment, we have the following metadata: *** SourceManufacturer: name of the headphones manufacturer (mandatory) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (mandatory). *** SourceURI: URI to the specs of the headphones (optional). == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 982c6983895a6c15fe96e12c48e7b72357e2c7c3 1796 1793 2014-07-24T20:46:56Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (mandatory) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (mandatory). *** SourceURI: URI to the specs of the headphones (optional). == Proposed version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} ab6b612eb2be593836db4ed169ac2b32263c2b1c 1797 1796 2014-07-24T20:47:41Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (mandatory) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (mandatory). *** SourceURI: URI to the specs of the headphones (optional). == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||HeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} fc2fc40a1d46a03e11999ba7641aee832cb3ef7e 1802 1797 2014-07-25T12:47:43Z Fbrinkmann 748 /* Previously proposed for HeadphoneIR, version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (mandatory) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (mandatory). *** SourceURI: URI to the specs of the headphones (optional). == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 73cd205212527457621fc6db867e14fef400af92 1812 1802 2014-08-11T09:52:41Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones will be a function of M. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (mandatory) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (mandatory). *** SourceURI: URI to the specs of the headphones (optional). *** ReceiverDescription: stores narrative information about the microphones (optional). *** EmitterDescription: stores narrative information about the headphones emitter (optional). == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} b52473a5a52d57497b51bf29f6d504ca0d94b12a 1813 1812 2014-08-11T10:42:25Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 776415b9ba849110986204cac6f5312b6bc02353 1814 1813 2014-08-11T10:46:43Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 701f14b753f2911ddd9c5fc559bfd1837a79e6fd 1815 1814 2014-08-11T10:50:56Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |- |GLOBAL:DatabaseName||||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||{''}||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||{''}||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||{''}||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||{''}||||MS||string||Optional M-dependent version of the attribute EmitterDescription |} == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} b57f8a36beceff2695caba791ccd5c939f0e4a3e 1816 1815 2014-08-11T11:03:35Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |- |GLOBAL:DatabaseName||||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||{&prime;&prime;}||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||{&prime;&prime;}||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||{&prime;&prime;}||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||{&prime;&prime;}||||MS||string||Optional M-dependent version of the attribute EmitterDescription |} == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 7087df9ccaad62c77fcb9e1ca2eea44e6a06365d 1817 1816 2014-08-11T11:04:38Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |- |GLOBAL:DatabaseName||||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||{&rsquo;&rsquo;}||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||{&rsquo;&rsquo;}||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||{&rsquo;&rsquo;}||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||{&rsquo;&rsquo;}||||MS||string||Optional M-dependent version of the attribute EmitterDescription |} == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} c2d7dc581115e85393d5484085eebd18f392269a 1818 1817 2014-08-11T11:08:55Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 -0.09 0; 0 0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 -0.09 0; 0 0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |} == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} aa292a5af3c248d656e7622adc827d00840d1f36 0 17 1800 1726 2014-07-25T08:45:34Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/listen LISTEN]: HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * '''New: [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ''' ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured within the project Club Fritz where several institutions measured the same artificial head. Coming soon... Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html e6a5f9120f9888cff9c91953e6ddcbbb9d626f68 0 15 1825 144 2014-09-05T16:48:38Z Petibub 4 wikitext text/x-wiki == API for Matlab/Octave == Currently, a [https://sourceforge.net/projects/sofacoustics/ API for Matlab and Octave] is available. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 20167909500e4182537d0853bda47c54e7a70098 1826 1825 2014-09-05T16:49:28Z Petibub 4 Petibub moved page [[APIs]] to [[Software and APIs]]: merging software and APIs wikitext text/x-wiki == API for Matlab/Octave == Currently, a [https://sourceforge.net/projects/sofacoustics/ API for Matlab and Octave] is available. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 20167909500e4182537d0853bda47c54e7a70098 1832 1826 2014-09-10T15:39:24Z Noisternig 5 /* API for Matlab/Octave */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab, Octave, and C++ is available online at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The C++ API is built on top of the C-based netCDF library. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 7d755bf824979312637b485cab5b585e2aab7ddf 1833 1832 2014-09-10T15:40:37Z Noisternig 5 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab, Octave, and C++ is available online at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 0d5993027481e96c3232e7e7ef54599c076e9246 0 471 1827 2014-09-05T16:49:28Z Petibub 4 Petibub moved page [[APIs]] to [[Software and APIs]]: merging software and APIs wikitext text/x-wiki #REDIRECT [[Software and APIs]] f24313a2e5e4cdfad01f6044e10775563fc6ba8e 0 1 1828 1736 2014-09-05T16:50:05Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: HRTFs of mannequins (dummy heads) measured using the same setup as for human listeners''' * [[Files|Files (HRTFs, BRIRs, DRIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 1d5c6afa8c7191231422a16c08f940212e6027df 0 11 1829 1711 2014-09-05T17:02:39Z Petibub 4 wikitext text/x-wiki == Specifications == * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ea5f97de339f3aa7252d6ae6446258a433a74756 1830 1829 2014-09-05T17:05:52Z Petibub 4 /* FIR */ wikitext text/x-wiki == Specifications == * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Additional delay of each IR in samples |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} 8da9b0527f3ae6b8c291831019ea9f46e0203ed4 0 16 1831 1721 2014-09-05T19:25:21Z Petibub 4 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader, Matlab support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Website support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): initiation of the [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) * '''Yukio Iwaya''' (Faculty of Engineering, Tohoku Gakuin University) * '''Michele Geronazzo''' (University of Padova): headphone support Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. Also you are invited to contact the standardization committee of X212. Join us at ([http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. d622138159476def0d155179a80238299dd23a77 1 472 1834 2014-09-18T18:30:33Z Petibub 4 Created page with "test" wikitext text/x-wiki test a94a8fe5ccb19ba61c4c0873d391e987982fbbd3 1 473 1835 2014-09-18T18:31:07Z Petibub 4 Created page with "test" wikitext text/x-wiki test a94a8fe5ccb19ba61c4c0873d391e987982fbbd3 6 474 1836 2014-09-24T11:41:50Z Petibub 4 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 11 1837 1830 2014-09-24T11:43:13Z Petibub 4 wikitext text/x-wiki == Specifications == * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Additional delay of each IR in samples |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} == Coordinate system == [[file:Coordinate_system.png]] e976427b364962ff6f4b234fdd6b7d9514e5ea09 0 16 1838 1831 2014-09-25T14:57:24Z Petibub 4 wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader, Matlab support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Website support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ API, specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): initiation of the [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) * '''Yukio Iwaya''' (Faculty of Engineering, Tohoku Gakuin University) * '''Michele Geronazzo''' (University of Padova): headphone support Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. Also you are invited to contact the standardization committee of X212. Join us at ([http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. bf05c8d2e04f34f2d2ed08b6b7064402c73acec4 0 17 1839 1800 2014-10-03T12:46:58Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/listen LISTEN]: HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured within the project Club Fritz where several institutions measured the same artificial head. Coming soon... Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. '''New: Headphone IRs (HpIRs) of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone inbetween) for over 100 listeners. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 69d4a5f5af17af9b82012deaab64d992140dadd8 1869 1839 2014-10-22T14:36:25Z Petibub 4 HpIRs from BT-DEI added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/listen LISTEN]: HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured within the project Club Fritz where several institutions measured the same artificial head. Coming soon... Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions. '''New: Headphone IRs (HpIRs) of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 4b27921801b9069fd024784ec1c1738c8723231d 1872 1869 2014-10-22T14:47:12Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/listen LISTEN]: HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured within the project Club Fritz where several institutions measured the same artificial head ''(Credit: Brian Katz)''. Coming soon... Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html f8da70580de6254547b677ad8631955f76ce2630 1873 1872 2014-10-22T14:48:10Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/listen LISTEN]: HRTFs from the [http://recherche.ircam.fr/equipes/salles/listen/download.html LISTEN] project, IRCAM. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured within the project Club Fritz where several institutions measured the same artificial head ''(Credit: Brian Katz, France)''. Coming soon... Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 86b018c63b862e8850d4f74c8d575e337632a2b0 0 1 1840 1828 2014-10-03T12:47:28Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Headphone IRs (HpIRs) for over 100 human listeners''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. 2e43f3a7588c9cef5fdf46bec8958356d0baeb09 1868 1840 2014-10-22T14:32:24Z Petibub 4 News history added wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Headphone IRs (HpIRs) for over 100 human listeners''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 47703af8eb8f2a02b26ae844f0e7114867905af3 1870 1868 2014-10-22T14:37:12Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Headphone IRs (HpIRs) for over 100 human listeners (ARI and BT-DEI databases)''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 4ad86ee9cadb2ee9874a6a5820ed33ad6b105a0b 1871 1870 2014-10-22T14:37:34Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Headphone IRs (HpIRs) for over 100 human listeners (ARI and BT-DEI databases)''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] SOFA has been proposed as a standard of the [http://aes.org Audio Engineering Society (AES)]. The standardization process ([http://www.aes.org/standards/meetings/init-projects/aes-x212-init.cfm X212]) is ongoing now and open for contributions. The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 24cb9611df856c253b2086de66ce038dc8c76c43 0 459 1841 1818 2014-10-03T13:24:55Z Petibub 4 /* Proposed version 0.1 */ wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Previously proposed for HeadphoneIR, version 0.1 == '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} ffbaa96d808a771a9b14ec2f086052207063b661 1884 1841 2014-10-31T13:32:07Z Hagenw 863 wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Previously proposed for HeadphoneIR, version 0.1 (deprecated) === '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 95370236f2c5299d2babbe61ece842f32108adcf 1885 1884 2014-10-31T13:32:36Z Hagenw 863 wikitext text/x-wiki Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Previously proposed for HeadphoneIR, version 0.1 (deprecated) === '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 8a87650644298f710ced6d299ca837c396cd24de 1886 1885 2014-10-31T13:35:13Z Hagenw 863 wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. == Proposed version 0.1 == [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Previously proposed for HeadphoneIR, version 0.1 (deprecated) === '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 0d4158ec0edc40409f9b47caa26969dfa2b816c0 0 5 1842 1768 2014-10-03T13:25:42Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with TF as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with FIR as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! f5559d7573da4ae9d3165977d4fecf309e1ec5a9 1855 1842 2014-10-13T15:26:32Z Tcarpent 862 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 87f3800ef281aa04ac36357db17c63cd8784c36d 1857 1855 2014-10-15T08:24:10Z Petibub 4 /* Proposed SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * ([[SimpleBRIR]]): Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 760d815c86c1127b21cb7a4b7a32724eac553f02 1876 1857 2014-10-31T13:13:54Z Hagenw 863 /* Proposed SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[MultiSpeakerBRIR]] * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! e42e72df8866ffdd4be0951b3027f56529a93335 1877 1876 2014-10-31T13:15:24Z Hagenw 863 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[HeadphoneIR]]: deprecated and will be replaced by [[SimpleHeadphoneIR]] ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[MultiSpeakerBRIR]] * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 775a48a69ba72388122718b9a4202a1af96d03ca 1878 1877 2014-10-31T13:16:05Z Hagenw 863 /* Stable SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * HeadphoneIR: deprecated and will be replaced by [[SimpleHeadphoneIR]] ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[MultiSpeakerBRIR]] * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! b241c5e113080d08236a7d87778421528e187b7c 1879 1878 2014-10-31T13:16:21Z Hagenw 863 /* Stable SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[HeadphoneIR]]: deprecated and will be replaced by [[SimpleHeadphoneIR]] ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[MultiSpeakerBRIR]] * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! cfd5b0f80d76ffb80846b2daac3cc16de2f7f0a7 1880 1879 2014-10-31T13:18:08Z Hagenw 863 /* Stable SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now in the latest official release of SOFA: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[HeadphoneIR]]: deprecated and will be replaced by [[SimpleHeadphoneIR]] ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[MultiSpeakerBRIR]] * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 6adb89cdcc65c5fd1faeb36204bcdb1a7e029f26 1881 1880 2014-10-31T13:19:30Z Hagenw 863 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now in the latest official release of SOFA: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[HeadphoneIR]]: deprecated and will be replaced by [[SimpleHeadphoneIR]] * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]] ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! c2b62af69a616b14b245b4d0d15fb2058d6a15f0 1882 1881 2014-10-31T13:20:49Z Hagenw 863 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now in the latest official release of SOFA: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[HeadphoneIR]]: deprecated and will be replaced by [[SimpleHeadphoneIR]] * [[MultiSpeakerBRIR]] * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 835aed046912230db7f79c45acd4416a26cfd749 1883 1882 2014-10-31T13:26:19Z Hagenw 863 /* Stable SOFA Conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now in the latest official release of SOFA: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[HeadphoneIR]]: deprecated and will be replaced by [[SimpleHeadphoneIR]] * [[MultiSpeakerBRIR]] * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 533cf4b1e33bcb7aea188e35b7ad49dab91dcd9b 1 475 1843 2014-10-08T16:48:26Z Petibub 4 Created page with "Here we can discuss Thibaut's suggestion to create a new data type." wikitext text/x-wiki Here we can discuss Thibaut's suggestion to create a new data type. 0b07b60515a3164a7ea27b96a2fbbbf090fe3f61 1844 1843 2014-10-13T14:25:39Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. dee18211d3113428805dbc7b9c657bb654191a8e 1845 1844 2014-10-13T14:26:27Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. b1d50963c52db9ee13d883837b5ceab6f16d453d 1846 1845 2014-10-13T14:32:57Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == Everything similar to SimpleFreeFieldHRIR except the following: For the sake of simplicity, we consider that all the filters is the cascade are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). DataType is 'SOS' Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. Data.Delay is [M R] and contains the monaural delay (in the units of N i.e. in samples). b5939c106336dc9da5209faffbac081728887b99 1847 1846 2014-10-13T14:33:13Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == Everything similar to SimpleFreeFieldHRIR except the following: For the sake of simplicity, we consider that all the filters is the cascade are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). DataType is 'SOS' Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. Data.Delay is [M R] and contains the monaural delay (in the units of N i.e. in samples). ec3d1909508f1647b5679e3b9ba7d45b9a808460 1848 1847 2014-10-13T14:34:16Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the filters is the cascade are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. Data.Delay is [M R] and contains the monaural delay (expressed in samples). 2eaa4655b25a518206f297e5ce183e8a1c183464 1849 1848 2014-10-13T14:37:28Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the filters is the cascade are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 0028d8566c3ddc0a7d92d550ca2a758687b25b73 1850 1849 2014-10-13T14:39:12Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the filters is the cascade are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 27fd55d3af5b1483bbec3b224cffadaa7b5bfecc 1851 1850 2014-10-13T14:41:49Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p) Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 666fbb632d67d5f2a31fa383ef9702f4edab3608 1852 1851 2014-10-13T14:42:09Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p) Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 7b295fa1e18ec56ceac9bda961d376e270488b8f 1853 1852 2014-10-13T14:46:14Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 39903d1d07e0713ee4eb3342dbad28ae37f29063 1854 1853 2014-10-13T14:47:11Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 68b18b637a3424c80330ed885d01e48d69729736 1856 1854 2014-10-13T19:45:15Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 0d4499a37483430ceaadcb0d36d861982e44b898 1859 1856 2014-10-15T08:25:12Z Petibub 4 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections == Data types == ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 6a369f46b39bd6f2eef0298241187d55a0847962 0 476 1858 2014-10-15T08:24:26Z Petibub 4 Created page with "insert the description of the convention here" wikitext text/x-wiki insert the description of the convention here d7e0aa1d0ef30ac2028bdc825b2c3ced1e3319d8 1860 1858 2014-10-15T09:16:57Z Tcarpent 862 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections == Data types == ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 6a369f46b39bd6f2eef0298241187d55a0847962 1861 1860 2014-10-15T09:19:00Z Tcarpent 862 /* Data types */ wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections == Data types == For storing second-order sections filters. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Delay in samples |} ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 841eb102154f2219784b00f4f11965697445e280 1862 1861 2014-10-15T09:19:25Z Tcarpent 862 /* Data types */ wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections == Data types == For storing second-order sections filters. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Monaural delay in samples |} ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 2dbdc8fd6852a14f91b292136742825da96fef4d 1863 1862 2014-10-15T09:20:37Z Tcarpent 862 /* Data types */ wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections == Data types == For storing second-order sections filters. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) d14ea8abe0ab55f16505765b9172eea69df1c9c6 1864 1863 2014-10-15T09:22:12Z Tcarpent 862 /* Data types */ wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections == Data types == For storing second-order sections filters. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOS filters (see below for details) |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) d377669d6ce54dc4f8d75c82f6f0148403b06f0b 1865 1864 2014-10-15T09:23:14Z Tcarpent 862 /* Data types */ wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections == Data type == === SOS === For storing second-order sections filters. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOS filters (see below for details) |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) f6d003eb7e20211ec0932a87f662bdc0268eea55 1866 1865 2014-10-15T09:27:55Z Tcarpent 862 /* Description */ wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections == Data type == === SOS === For storing second-order sections filters. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOS filters (see below for details) |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} ==Description== This convention is essentially the same as SimpleFreeFieldHRIR except that it is adapted to a parametric model of HRIR. This parametric model consists of replacing HRIR (as FIR) with a monaural delay and second order sections filters. The 'Parents' attribute may be used to refer to the SimpleFreeFieldHRIR file (if any) that was the origin of the parametric model. ==Background== Being a causal and stable filter, an HRIR can be decomposed into a minimum phase part component and an all-pass component. The phase of each HRIR is thus decomposed into the minimum phase and the phase of the all-pass component i.e. the excess phase. The minimum phase is related to the magnitude spectrum through the Hilbert transform. The excess phase of HRIR is usually linear (up to approx 8 - 10 kHz). A simplified model of HRTF can thus be built where the all-pass component is replaced by a pure delay. This pure delay is referred to as monaural delay. Each HRTF is thus fully described by its magnitude spectrum and the monaural delay. Several perceptual studies (e.g. Wightman 1992) have shown the validity of such simplified model (given the fact that the phase information of the higher frequencies -- that is neglected by the model -- is not used by the auditory system to estimate the directions of arrival). Finally the minimum phase part of HRTF can be modeled as an IIR filter. Many modeling techniques have been proposed. Anyway the resulting IIR digital filter needs to be represented as a cascade of first order or second order sections for numerical stability reasons. ==Proposal for SimpleFreeFieldSOS == For the sake of simplicity, we consider that all the cascaded filters are second order filters (i.e. no first order filter). (anyway a first order filter can be represented with a second order filter). The SOS is represented as follows: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections. Each second order section is represented by 6 filter taps: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) (even though the denominator is usually normalized such that ai0 = 1). For each filter H(z), the filter taps are arranged as follows: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b10 b11 b12 a10 a11 a12 b20 b21 b22 a20 a21 a22 .... bp0 bp1 bp2 ap0 ap1 ap2 ] SimpleFreeFieldSOS convention : everything similar to SimpleFreeFieldHRIR except the following: DataType is 'SOS' (standing for 'second order sections'). Data.SOS of size [ M R N ] contains the filter coefficients. N being the total number of coefficients, it is always a multiple of 6. (N = 6 * p). The SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. Data.Delay is [M R] and contains the monaural delay (expressed in samples). We encourage to use the 'History' attribute to store informations relative to the modelization process (algorithm(s) used to derive the IIR model, method used to estimate the monaural delays, etc.) 1268670cde0408791cf2efda85defda081ee9334 6 470 1867 1771 2014-10-22T10:40:05Z Petibub 4 Petibub uploaded a new version of &quot;[[File:SimpleHeadphoneIR-0.1.png]]&quot;: default values for the coordinates fixed wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 9 1874 1713 2014-10-31T11:47:43Z Petibub 4 marking older versions as deprecated wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the currently most recent version, we adapted the Conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). == Version 0.4 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Proposed for version 0.3 (deprecated) == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Version 0.2 (deprecated) == [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Version 0.1 (deprecated) == {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 265c041ca5f5abf41341112ad84521d8b68ea944 1875 1874 2014-10-31T12:40:53Z Hagenw 863 wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the currently most recent version, we adapted the Conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). == Version 0.4 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 452c3cd93cece6b5f9a60b22ef1bf541b9086881 0 24 1887 1714 2014-10-31T13:38:26Z Hagenw 863 wikitext text/x-wiki == Description == This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is TF. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. == Version 0.4 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldTF||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldTF Convention are listed below. === Version 0.3 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} 467acfd5e070abe0fb4a9db77e0aeeb349377f2c 1888 1887 2014-10-31T13:39:30Z Hagenw 863 wikitext text/x-wiki == Description == This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is TF. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. == Version 0.4 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldTF||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldTF Convention are listed below. === Version 0.3 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} 40078b09a41b811ec24881d9de8c0e77ced515c1 1924 1888 2015-05-12T08:32:17Z Petibub 4 wikitext text/x-wiki == Description == This SOFA Conventions is similar to [[SimpleFreeFieldHRIR]]. The most apparent difference is the DataType, which is TF. This Conventions was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. == Version 1.0 == This version follows the standardized conventions SimpleFreeFieldHRIR (version 1.0). Note that it is, in contrast to SimpleFreeFieldHRIR 1.0 not included in the standard, thus it is declared as stable. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldTF</nowiki>||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||||||attribute|| |} == Old deprecated versions == === Version 0.4 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldTF||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldTF Convention are listed below. === Version 0.3 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} 47681e162566fd44166f9ed971ee77ed9d0f153c 1925 1924 2015-05-12T08:34:57Z Petibub 4 wikitext text/x-wiki == Description == This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is TF, not FIR. SimpleFreeFieldTF was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldTF, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldTF</nowiki>||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||||||attribute|| |} == Old deprecated versions == For historical reasons the older versions of the SimpleFreeFieldTF conventions are listed below. === Version 0.4 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldTF||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} === Version 0.3 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} 16213e056303c35377e264c171c924c0e6614ba0 1933 1925 2015-05-12T08:58:59Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki == Description == This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is TF, not FIR. SimpleFreeFieldTF was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldTF 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldTF</nowiki>||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||||||attribute|| |} == Old deprecated versions == For historical reasons the older versions of the SimpleFreeFieldTF conventions are listed below. === Version 0.4 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldTF||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} === Version 0.3 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} 91393fb8aeb4aae7f28ad05b2fddda932bf49461 1934 1933 2015-05-12T08:59:31Z Petibub 4 wikitext text/x-wiki == Description == This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is TF, not FIR. SimpleFreeFieldTF was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldTF 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldTF</nowiki>||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||||||attribute|| |} == Old deprecated versions == For historical reasons the older versions of the SimpleFreeFieldTF conventions are listed below. === Version 0.4 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldTF||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} === Version 0.3 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} 11b2600ab7ec48a936b4536f5cc89f3b76bd1e61 0 25 1889 1692 2014-10-31T13:41:17Z Hagenw 863 wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This conventions defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. == Version 0.1 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomDRIR||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||reverberant||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute|| |- |GLOBAL:RoomDescription||||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView||[-1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 9ea1012fb35e5e63d813943f652d323362a0872b 1926 1889 2015-05-12T08:36:50Z Petibub 4 wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This convention set defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. == Version 0.3 == This version uses SOFA 1.0 which reflects the standard AES69-2015. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomDRIR</nowiki>||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView||<nowiki>[-1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomDRIR||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||reverberant||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute|| |- |GLOBAL:RoomDescription||||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView||[-1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} bb64c9cbd648236db9900d2588a4d7e822b3afc2 1931 1926 2015-05-12T08:57:02Z Petibub 4 wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This convention set defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. == Version 0.3 == This version uses SOFA 1.0 which reflects the standard AES69-2015. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomDRIR</nowiki>||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView||<nowiki>[-1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomDRIR||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||reverberant||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute|| |- |GLOBAL:RoomDescription||||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView||[-1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} c63f9921d4855b807c676dd116dc71324e2e298a 0 11 1890 1837 2014-11-04T10:01:30Z Petibub 4 FIRE added wikitext text/x-wiki == Specifications == * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR in samples |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR in samples |} == Coordinate system == [[file:Coordinate_system.png]] 6c67ae38924f60ca51745d0a99777d87d94bb113 1891 1890 2014-11-04T10:01:48Z Petibub 4 /* Data Types */ wikitext text/x-wiki == Specifications == * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR in samples |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR in samples |} == Coordinate system == [[file:Coordinate_system.png]] 59396a935d9116b3d40b0e65574f7b7586690760 1895 1891 2014-11-12T14:48:48Z Petibub 4 /* FIRE */ wikitext text/x-wiki == Specifications == * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR in samples |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} == Coordinate system == [[file:Coordinate_system.png]] a01c9a18c965c380240109bebc27979ab024c91f 1896 1895 2014-11-12T14:48:59Z Petibub 4 /* FIR */ wikitext text/x-wiki == Specifications == * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} == Coordinate system == [[file:Coordinate_system.png]] 2df960bf9c810b2d09f174e59ab47a73f17add9a 1897 1896 2014-11-12T14:49:14Z Petibub 4 /* FIRE */ wikitext text/x-wiki == Specifications == * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download Version 0.6: Download specifications] Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} == Coordinate system == [[file:Coordinate_system.png]] 847b130affc515bc62667abf1756c96b2a85f5f0 1910 1897 2015-05-08T16:46:30Z Petibub 4 /* Specifications */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} == Coordinate system == [[file:Coordinate_system.png]] 9a37dde8c39e72d43d3c2e3e8940291eddfced6f 1911 1910 2015-05-08T16:47:47Z Petibub 4 /* FIR */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} == Coordinate system == [[file:Coordinate_system.png]] c83fff3f1fa60b6ca6b8a45301bd04ff8013ed68 1912 1911 2015-05-08T16:48:05Z Petibub 4 /* TF */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} == Coordinate system == [[file:Coordinate_system.png]] 39553ff62c973c8186f96736b8ed4cd23a3bdec0 1913 1912 2015-05-08T16:48:19Z Petibub 4 /* FIRE */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Archive: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} == Coordinate system == [[file:Coordinate_system.png]] 2769d3f09b7fa2669f3cea387e3c05d9cd342951 1914 1913 2015-05-08T16:49:01Z Petibub 4 /* Specifications */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} == Coordinate system == [[file:Coordinate_system.png]] abaa7c2cef090ca454f41009bbfca6c946b35f97 1915 1914 2015-05-08T16:49:39Z Petibub 4 wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 5416a968239eb8886ae00195af51691d4c1d417d 0 477 1892 2014-11-04T10:13:07Z Petibub 4 MultiSpeakerBRIR added wikitext text/x-wiki ==Description== This conventions was developed for binaural room impulse responses (BRIRs) measured in a multispeaker setup (=multiple emitters). It is based on SimpleFreeFieldHRIR with the most striking difference of using the '''FIRE''' as DataType. This allows to more compactly describe the data for all involved emitters. == Version 0.2 == In this version, we explicitly use the Datatype FIRE. Also, the size of E is defined by the size Data, which is consistent with other SOFA conventions. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} == Old, deprecated versions == === Version 0.1 === This was the first version, it used FIR datatype which was inofficially extended by E. Also, the comment said that EmitterPosition determines the size of E, which is deprecated as well. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} a597868dc3d5e55cf55cf10a5d371dcb35a10395 1894 1892 2014-11-12T14:46:59Z Petibub 4 Data.Delay dimensions fixed wikitext text/x-wiki ==Description== This conventions was developed for binaural room impulse responses (BRIRs) measured in a multispeaker setup (=multiple emitters). It is based on SimpleFreeFieldHRIR with the most striking difference of using the '''FIRE''' as DataType. This allows to more compactly describe the data for all involved emitters. == Version 0.2 == In this version, we explicitly use the Datatype FIRE. Also, the size of E is defined by the size Data, which is consistent with other SOFA conventions. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} == Old, deprecated versions == === Version 0.1 === This was the first version, it used FIR datatype which was inofficially extended by E. Also, the comment said that EmitterPosition determines the size of E, which is deprecated as well. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} e1e0a139089ba672d2029f42676c1420e98a7c49 1901 1894 2014-11-16T19:07:57Z Petibub 4 /* Version 0.2 */ wikitext text/x-wiki ==Description== This conventions was developed for binaural room impulse responses (BRIRs) measured in a multispeaker setup (=multiple emitters). It is based on SimpleFreeFieldHRIR with the most striking difference of using the '''FIRE''' as DataType. This allows to more compactly describe the data for all involved emitters. == Version 0.2 == In this version, we explicitly use the Datatype FIRE. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} == Old, deprecated versions == === Version 0.1 === This was the first version, it used FIR datatype which was inofficially extended by E. Also, the comment said that EmitterPosition determines the size of E, which is deprecated as well. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} 4b89fb3d14654839fc587730fe973781f5b2e0ec 1923 1901 2015-05-12T08:29:29Z Petibub 4 wikitext text/x-wiki ==Description== This conventions was developed for binaural room impulse responses (BRIRs) measured in a multispeaker setup (=multiple emitters). It is based on SimpleFreeFieldHRIR with the most striking difference of using the '''FIRE''' as DataType. This allows to more compactly describe the data for all involved emitters. == Version 0.3 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} == Old deprecated versions == === Version 0.2 === In this version, we explicitly use the Datatype FIRE. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} == Old, deprecated versions == === Version 0.1 === This was the first version, it used FIR datatype which was inofficially extended by E. Also, the comment said that EmitterPosition determines the size of E, which is deprecated as well. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} 178f87f9d21edbf601ec26918c70101f9f516d40 1932 1923 2015-05-12T08:58:01Z Petibub 4 wikitext text/x-wiki ==Description== This conventions was developed for binaural room impulse responses (BRIRs) measured in a multispeaker setup (=multiple emitters). It is based on SimpleFreeFieldHRIR with the most striking difference of using the '''FIRE''' as DataType. This allows to more compactly describe the data for all involved emitters. == Version 0.3 == This version uses SOFA 1.0 which reflects the standard AES69-2015. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} == Old deprecated versions == === Version 0.2 === In this version, we explicitly use the Datatype FIRE. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} === Version 0.1 === This was the first version, it used FIR datatype which was inofficially extended by E. Also, the comment said that EmitterPosition determines the size of E, which is deprecated as well. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} 4f7c193e32d06b743ba930e33783ed85af73ea5b 0 17 1893 1873 2014-11-07T13:10:01Z Tcarpent 862 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured within the project Club Fritz where several institutions measured the same artificial head ''(Credit: Brian Katz, France)''. Coming soon... Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 541b1953b48d56159b6413332c751ed19755905f 1907 1893 2015-04-21T10:56:37Z Petibub 4 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * '''New:''' [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured within the project Club Fritz where several institutions measured the same artificial head ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 07a69207cbb321afad9f5c11229727adec72e42a 1908 1907 2015-04-21T11:31:33Z Bfgkatz 869 /* General purpose database: */ Fritz update wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * '''New:''' [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)] ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo sofa_api_mo] HRTFs as examples for the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html f4aefca1727bef2ccf8b7f5884be0a09d5e1a7e7 0 5 1898 1883 2014-11-14T10:39:52Z Verade 864 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. ==Stable SOFA Conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by a software package. The following stable SOFA conventions are available now in the latest official release of SOFA: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[HeadphoneIR]]: deprecated and will be replaced by [[SimpleHeadphoneIR]] * [[MultiSpeakerBRIR]] * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. ==Proposed SOFA Conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. == Unsorted topics == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 3f9d8ee6ac13792e6346f49ed7460cfe08b469a4 1916 1898 2015-05-08T16:59:00Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification of one these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType) * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[MultiSpeakerBRIR]] * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[HeadphoneIR]]: deprecated, replaced by [[SimpleHeadphoneIR]] These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 3574e24f02a2cd80e9d8a8a956e71cd48d5a6345 1927 1916 2015-05-12T08:50:32Z Petibub 4 /* Stable SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification of one these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType) * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: Room impulse responses measured with an arbitrary number of receivers (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]] These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 70603f11cea36482c2b617ba422e1e16d149edfd 0 478 1899 2014-11-14T15:02:16Z Petibub 4 Created page with "test" wikitext text/x-wiki test a94a8fe5ccb19ba61c4c0873d391e987982fbbd3 1900 1899 2014-11-14T15:59:57Z Verade 864 wikitext text/x-wiki ==Description== This convention defines only that FIRE is the DataType. All other metadata follow the general SOFA specifications. This convention can be used to save data which are too general to store in more specific conventions. == Version 0.1 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 4c00e198279d03e23d02e36fba2fcb84f3f406ea 1920 1900 2015-05-12T08:06:53Z Petibub 4 wikitext text/x-wiki ==Description== This convention defines only that FIRE is the DataType. All other metadata follow the general SOFA specifications. This convention can be used to save data which are too general to store in more specific conventions. == Version 0.2 == This version uses SOFA 1.0. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} == Version 0.1 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} c1de7be5f04a9d5aa5a66beaf97f9808d3cd2390 1921 1920 2015-05-12T08:07:58Z Petibub 4 /* Version 0.1 */ wikitext text/x-wiki ==Description== This convention defines only that FIRE is the DataType. All other metadata follow the general SOFA specifications. This convention can be used to save data which are too general to store in more specific conventions. == Version 0.2 == This version uses SOFA 1.0. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} aecae3ec7b5e0516ac214ff47ebcfbb26078467f 1935 1921 2015-05-12T09:01:53Z Petibub 4 wikitext text/x-wiki ==Description== This convention defines only that FIRE is the DataType. All other metadata follow the general SOFA specifications. This convention can be used to save data which are too general to store in more specific conventions. == Version 0.2 == This version uses SOFA 1.0. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 8e51ab4cc73eb81f029c15ef88916cf4cd1d2031 1936 1935 2015-05-12T09:11:58Z Petibub 4 wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[GeneralFIR]]. The only difference is the DataType, which is FIR'''E''', not FIR. All other attributes and variables follow the general SOFA specifications. As GeneralFIR, this convention set can be used to save data which are too general to store in more specific conventions. == Version 0.2 == This version follows the conventions [[GeneralFIR]] (version 1.0) standardized in AES69-2015. Note that GeneralFIRE 1.0, in contrast to GeneralFIR 1.0, has not been included in the standard, thus, here, we declare it as stable. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 755a9de358ccd9e4e76fa93da9fb7c945ebddf35 0 9 1902 1875 2014-12-17T14:47:52Z Petibub 4 /* Version 0.4 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.3, we assume the listener being in the center of the measurement setup, and the source moving around the listener in order to represent the different HRTF directions. Further, the apparent position vector, APV, can be used to more simple provide the apparent position for each measured HRTFs. Note that with SimpleFreeFieldHRIR version 0.3, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the currently most recent version, we adapted the Conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). == Version 0.4 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ca64af4dc10dfdfa3cd157052b2d5586f61d6bc1 1903 1902 2014-12-17T18:31:29Z Petibub 4 /* Description */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.4, we use SourcePosition to represent the different HRTF directions. By doing so, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the currently most recent version, we adapted the conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). == Version 0.4 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 0a49e5186bf6da28f953c2a5a2067a7d780ac07c 1919 1903 2015-05-11T19:39:26Z Petibub 4 wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.4, we use SourcePosition to represent the different HRTF directions. By doing so, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the last version before AES69-2015, we adapted the conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). SimpleFreeFieldHRIR version 1.0 represents the current standardized convention set from AES69-2015. == Version 1.0 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This convention set essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This convention set can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRIR</nowiki>||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. == Version 0.4 (deprecated) == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} Legend: * '''Name''': the name of the metadata ** An underscore (_): the metadata is an attribute *** GLOBAL_: the metadata is a global attribute *** X_Y: the metadata is an attribute Y of the variable X ** No underscore: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) ca082cf5088d3e1c693c64ac7ec026df8b71707d 1930 1919 2015-05-12T08:56:12Z Petibub 4 wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.4, we use SourcePosition to represent the different HRTF directions. By doing so, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the last version before AES69-2015, we adapted the conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). SimpleFreeFieldHRIR version 1.0 represents the current standardized convention set from AES69-2015. == Version 1.0 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This convention set essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This convention set can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRIR</nowiki>||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Version 0.4 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 33e255ac71633430c55e02e05b57cc1e4ed66faf 0 15 1904 1833 2015-03-24T12:49:57Z Petibub 4 /* API for Matlab/Octave */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab, Octave, and C++ is available online at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. '''Note: This API has not been updated to the recently published standard AES69-2015. The update is scheduled for ASAP. ''' If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 7d19de8b064c9cdf9d8cedd092207efc9ada53ad 1905 1904 2015-03-24T13:50:54Z Noisternig 5 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab, Octave, and C++ is available online at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. '''Note: The Matlab/Octave APIs have not been updated to the recently published standard AES69-2015. The update to version 1.0 is scheduled for ASAP. The latest version of the C++ API (version 1.0) is in accordance with the AES69-2015 standard. ''' If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 7d8b86dcc77130e481c7a6a80b429d49fb489f0a 1906 1905 2015-03-24T13:52:48Z Noisternig 5 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab, Octave, and C++ is available online at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. '''Note: * The Matlab/Octave APIs (version 0.4.3) have not been updated to the recently published standard AES69-2015. The update to version 1.0 is scheduled for ASAP. * The latest version of the C++ API (version 1.0) is in accordance with the AES69-2015 standard. ''' If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 0c7089ded8f0e4182698cf8ac0f410a26c99c2ab 0 1 1909 1871 2015-05-08T16:43:08Z Petibub 4 AES69-2015 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Headphone IRs (HpIRs) for over 100 human listeners (ARI and BT-DEI databases)''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released e526611884aeb1ed1bf49cdb3736ed87420e18a7 0 286 1917 705 2015-05-11T19:31:01Z Petibub 4 wikitext text/x-wiki This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 682303884d9548bfa08b76e4e0085a5dac486bbb 0 287 1918 706 2015-05-11T19:32:16Z Petibub 4 wikitext text/x-wiki This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} Legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) 536b3edad6abb005dccccc60227941330fd7ca78 0 459 1922 1886 2015-05-12T08:11:03Z Petibub 4 wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 0.2 == This version uses SOFA 1.0 representing the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Previously proposed for HeadphoneIR, version 0.1 (deprecated) === '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} == Old deprecated versions == === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Previously proposed for HeadphoneIR, version 0.1 (deprecated) === '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 420898d9e067daf754c84d87807b25276f127a13 1928 1922 2015-05-12T08:53:26Z Petibub 4 wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 0.2 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Version 0.1, previously proposed as HeadphoneIR (deprecated) === '''This conventions proposal is deprecated - a new proposal is currently under development. Contribute by discussing with us (use the "Discussion" tab).''' {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} 492d48e75f10a7a80db1925de9cf97ca49c78caa 1929 1928 2015-05-12T08:53:55Z Petibub 4 /* Version 0.1, previously proposed as HeadphoneIR (deprecated) */ wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 0.2 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Version 0.1, previously proposed as HeadphoneIR (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} 1b46dd619ba4c8aa1827e28fa12f7260aa440686 0 17 1937 1908 2015-05-12T09:15:25Z Petibub 4 /* Special purpose: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * '''New:''' [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)] ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 6cca49068bde977202568a583e64e1ca29dc9d66 1984 1937 2015-06-18T14:24:14Z Petibub 4 Tuburo added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 100 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. * '''New:''' [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 580f28daf873570e9c4c9af10a4040319868362e 0 11 1938 1915 2015-05-12T09:35:39Z Petibub 4 /* Data Types */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is nominator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi0 + bi1 z^(-1) + bi2 z^(-2) Ai(z) = ai0 + ai1 z^(-1) + ai2 z^(-2) Note that usually, Ai(z) is normalized such that ai0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * SamplingRate: sampling rate used to describe the filter. * Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * SOS: list of coefficients of all SOSs represented as a list: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOSs |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} 47acaa7b09901e6a462860d53bb83d7138a3ef68 1939 1938 2015-05-12T09:37:29Z Petibub 4 wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is nominator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * SamplingRate: sampling rate used to describe the filter. * Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * SOS: list of coefficients of all SOSs represented as a list: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOSs |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} 6c8758f2b7fb57c9d2f7fc9d2698693f547221d0 1940 1939 2015-05-12T09:47:31Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is nominator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. Data.SOS: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOSs |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} acf0defd7b6c86996caf99e3c72aff39ad730f76 1941 1940 2015-05-12T11:03:29Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is nominator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. Data.SOS: [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] == [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOSs |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} 05b19d490b600bcff6e576786d3b68b545a0df72 1944 1941 2015-05-12T11:18:49Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is nominator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. The format of the list is: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOSs |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} 1ba56e81c7e5cd10571668de348679b122991cd5 1945 1944 2015-05-12T14:05:55Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. The format of the list is: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[1 1]</nowiki>||m||mRn||double||Coefficients of the SOSs |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||MR||double||Monaural delay in samples |} 6bd253ea73476526c438e474e4c9135be408ef98 1955 1945 2015-05-12T15:11:19Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. The format of the list is: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>0</nowiki>||m||mRn||double||Coefficients of the SOSs |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Monaural delay in samples |} bcad1bc702288570e84d4ab62bc85dc8e9557fcb 1956 1955 2015-05-12T15:13:03Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. The format of the list is: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>0</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.SOS |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 504c0375586bdf9c24c84c5444160bafa8ae93d3 1957 1956 2015-05-12T15:13:45Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. The format of the list is: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>0</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} eb0d76261898dc8ff7f4815dfef975bfb32ebaad 1973 1957 2015-05-13T12:12:59Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. The format of the list is: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>[0 0 0 1 0 0]</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} e74446b95a0eb375364fbde2b87bcb1d58b95d6e 1976 1973 2015-05-13T12:38:58Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of [ M R N ] with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. The format of the list is: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 007e6da8f272c85775268edee490c87e0141c538 1977 1976 2015-05-13T12:39:34Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. Data.SOS has the size of '''[ M R N ]''' with N being the total number of coefficients. N is an integer multiple of 6 and corresponds to 6p. The format of the list is: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 953297497e9fce59ddf771c139b42173b4ecc929 1978 1977 2015-05-13T12:41:44Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to 6p. ** Format of the list: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 51d9e48f83148d5738ba51ac540db4f21df47324 1979 1978 2015-05-13T12:42:13Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to 6p. ** Format of the list: Along the dimension N, the list goes like: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 3f284d33640f51fee8756ea4567c7dbddf25f2bb 1985 1979 2015-06-24T12:41:18Z Petibub 4 Testing math module wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: H(z) = B1(z) / A1(z) . B2(z) / A2(z) . ... . Bp(z) / Ap(z) where p is the number of second order sections, A(z) is denominator representing the poles of a filter, and B(z) is numerator representing the zeros of a filter. Then, each SOS can be described as: Bi(z) = bi,0 + bi,1 z^(-1) + bi,2 z^(-2) Ai(z) = ai,0 + ai,1 z^(-1) + ai,2 z^(-2) Note that usually, Ai(z) is normalized such that ai,0 = 1. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to 6p. ** Format of the list: Along the dimension N, the list goes like: [ b1,0 b1,1 b1,2 a1,0 a1,1 a1,2 b2,0 b2,1 b2,2 a2,0 a2,1 a2,2 .... bp,0 bp,1 bp,2 ap,0 ap,1 ap,2 ] which corresponds to [ B1(z) A1(z) B2(z) A2(z) .... Bp(z) Ap(z) ] {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} Test: <math>\int\limits_a^x f(\frac{\alpha}{2}\,)\,dx</math> 63fa2c488339984e3ca0695d953753eae1b87998 0 476 1942 1866 2015-05-12T11:06:45Z Petibub 4 wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is SOS, not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. We encourage to use the 'History' attribute to store information about the creation of SOSs and estimation of delay from the underlying filters. Also, 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. a7c57c35260aaa2d051d1c271f60a546df28699f 1943 1942 2015-05-12T11:07:42Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki SimpleFreeFieldSOS : Simple Free Field Second Order Sections ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is SOS, not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. 369912471e15a252da0dd48efafac2bcf78720e7 1954 1943 2015-05-12T14:49:37Z Petibub 4 wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is SOS, not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. e1a4aefdf7f461adfaf78f932540978e6a15e4b1 1958 1954 2015-05-12T19:58:05Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is SOS, not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>0</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} 1bdca40e548884044471ed4ca1afc7e215d6e9e4 1959 1958 2015-05-13T11:52:02Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is SOS, not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||m||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>[1 0 0 1 0 0] </nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} fd70d70a618c9ba07703939607e58800d6732c61 1970 1959 2015-05-13T12:10:06Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is SOS, not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>[1 0 0 1 0 0] </nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} 1a2d3a05640e9f27ec40cd29715d6a2eafec9a55 1974 1970 2015-05-13T12:24:13Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is SOS, not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>[0 0 0 1 0 0; 0 0 0 1 0 0] </nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} c8082faaff9591457a3d17d684461c50804fa5d0 1975 1974 2015-05-13T12:34:38Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is SOS, not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} 99bafbcb288baea5abc5cd15b5195237242b6b4e 6 479 1946 2015-05-12T14:41:29Z Petibub 4 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1947 1946 2015-05-12T14:42:12Z Petibub 4 Petibub uploaded a new version of &quot;[[File:MultiSpeakerBRIR-0.3.png]]&quot; wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1948 1947 2015-05-12T14:44:14Z Petibub 4 Petibub uploaded a new version of &quot;[[File:MultiSpeakerBRIR-0.3.png]]&quot; wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 477 1949 1932 2015-05-12T14:44:47Z Petibub 4 /* Description */ wikitext text/x-wiki ==Description== [[File:MultiSpeakerBRIR-0.3.png|right|thumb|225px]] This conventions was developed for binaural room impulse responses (BRIRs) measured in a multispeaker setup (=multiple emitters). It is based on SimpleFreeFieldHRIR with the most striking difference of using the '''FIRE''' as DataType. This allows to more compactly describe the data for all involved emitters. == Version 0.3 == This version uses SOFA 1.0 which reflects the standard AES69-2015. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} == Old deprecated versions == === Version 0.2 === In this version, we explicitly use the Datatype FIRE. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} === Version 0.1 === This was the first version, it used FIR datatype which was inofficially extended by E. Also, the comment said that EmitterPosition determines the size of E, which is deprecated as well. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} cfbd91a6429acae17478862f619295aace13cc8f 1972 1949 2015-05-13T12:12:13Z Petibub 4 /* Version 0.3 */ wikitext text/x-wiki ==Description== [[File:MultiSpeakerBRIR-0.3.png|right|thumb|225px]] This conventions was developed for binaural room impulse responses (BRIRs) measured in a multispeaker setup (=multiple emitters). It is based on SimpleFreeFieldHRIR with the most striking difference of using the '''FIRE''' as DataType. This allows to more compactly describe the data for all involved emitters. == Version 0.3 == This version uses SOFA 1.0 which reflects the standard AES69-2015. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} == Old deprecated versions == === Version 0.2 === In this version, we explicitly use the Datatype FIRE. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} === Version 0.1 === This was the first version, it used FIR datatype which was inofficially extended by E. Also, the comment said that EmitterPosition determines the size of E, which is deprecated as well. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} 9a45458833cd90f755948df0e6339d81319a2e9a 0 5 1950 1927 2015-05-12T14:46:47Z Petibub 4 /* Stable SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification of one these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType) * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 7a7be0e3c5e72892eb2b4515ff491be06605cf6c 1951 1950 2015-05-12T14:47:34Z Petibub 4 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification of one these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType) * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 6fa8fb32cb8b2b2e0f3613e4a38c56310750e209 1952 1951 2015-05-12T14:48:17Z Petibub 4 /* Stable SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification of one these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! aa2fc787e28bc762fd43906d564f80b7631360c7 1953 1952 2015-05-12T14:49:00Z Petibub 4 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! ee1d99230127ddfc9add20d92b320e9b6dfc0dc3 1960 1953 2015-05-13T12:02:23Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Legend for the tables showing conventions Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! b156797c445a745af6cab2c36f5a640082e0508d 1961 1960 2015-05-13T12:02:40Z Petibub 4 /* Ideas for future conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Legend for the tables showing conventions == Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 13ac0053eb9d7cdbcccb482cf0d1cf9cdefe9e19 1962 1961 2015-05-13T12:03:32Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! e18cd5734497cf1fbce31f53ddc819c1ef947e4d 1963 1962 2015-05-13T12:04:31Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 2482e873ec167c3b5daa34b8d7480abb1bd6c95a 0 286 1964 1917 2015-05-13T12:04:53Z Petibub 4 wikitext text/x-wiki This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |} 650e2db0449174e8909e1a85f0e53e269cef31f0 0 287 1965 1918 2015-05-13T12:05:19Z Petibub 4 wikitext text/x-wiki This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 907805726b0faa8fcce1e4f499f89097f0dbc53d 0 9 1966 1930 2015-05-13T12:06:07Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.4, we use SourcePosition to represent the different HRTF directions. By doing so, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the last version before AES69-2015, we adapted the conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). SimpleFreeFieldHRIR version 1.0 represents the current standardized convention set from AES69-2015. == Version 1.0 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This convention set essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This convention set can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRIR</nowiki>||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Version 0.4 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 1946c19d65a888e3a7354b6be1e9346652085f86 0 478 1967 1936 2015-05-13T12:06:50Z Petibub 4 /* Version 0.2 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[GeneralFIR]]. The only difference is the DataType, which is FIR'''E''', not FIR. All other attributes and variables follow the general SOFA specifications. As GeneralFIR, this convention set can be used to save data which are too general to store in more specific conventions. == Version 1.0 == This version follows the conventions [[GeneralFIR]] (version 1.0) standardized in AES69-2015. Note that GeneralFIRE 1.0, in contrast to GeneralFIR 1.0, has not been included in the standard, thus, here, we declare it as stable. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 61b65a55aec51fad750b62b96bc518d3666fa6ae 0 459 1968 1929 2015-05-13T12:07:23Z Petibub 4 /* Version 0.2 */ wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 0.2 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Version 0.1, previously proposed as HeadphoneIR (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} 4826ad902449f9838030c197e767beb5c6a2358a 0 24 1969 1934 2015-05-13T12:07:47Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki == Description == This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is TF, not FIR. SimpleFreeFieldTF was requested to cover the needs coming from HRTF simulations where results are given as complex values in the frequency domain for some discrete frequencies. == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldTF 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldTF</nowiki>||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||||||attribute|| |} == Old deprecated versions == For historical reasons the older versions of the SimpleFreeFieldTF conventions are listed below. === Version 0.4 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldTF||rm||||attribute||This conventions is for TFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} === Version 0.3 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |Data.Real||[1 1]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} cfd141da73ffa7dd8ef286623b8824d6c3c35ea3 0 25 1971 1931 2015-05-13T12:11:29Z Petibub 4 /* Version 0.3 */ wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This convention set defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. == Version 0.3 == This version uses SOFA 1.0 which reflects the standard AES69-2015. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomDRIR</nowiki>||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView||<nowiki>[-1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomDRIR||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||reverberant||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute|| |- |GLOBAL:RoomDescription||||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView||[-1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 6c623618e1b693296d46ee1286d6929fd65d0445 0 15 1980 1906 2015-05-13T13:17:18Z Petibub 4 /* API for Matlab/Octave */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab, Octave, and C++ is available online at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. '''Note: * The Matlab/Octave APIs (version 0.4.3) does not fully support the recently published standard AES69-2015. The full support is provided with the version 1.0, which is now in the stage of release candidate 2 (1.0RC2). * The latest version of the C++ API (version 1.0) is in accordance with the AES69-2015 standard. ''' If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. cb58723f27cf8052e640973689456661a36e761c 1981 1980 2015-05-13T13:18:48Z Petibub 4 /* API for Matlab/Octave */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab, Octave, and C++ is available online. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics github] '''Note: * The Matlab/Octave APIs (version 0.4.3) does not fully support the recently published standard AES69-2015. The full support is provided with the version 1.0, which is now in the stage of release candidate 2 (1.0RC2). * The latest version of the C++ API (version 1.0) is in accordance with the AES69-2015 standard. ''' If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. c3ce74ebe73ea0d1cc9359a8b148c3de34f6ba6f 1982 1981 2015-05-13T13:19:20Z Petibub 4 /* API for Matlab/Octave */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave, and C++ is available online. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics github] '''Note: * The Matlab/Octave APIs (version 0.4.3) does not fully support the recently published standard AES69-2015. The full support is provided with the version 1.0, which is now in the stage of release candidate 2 (1.0RC2). * The latest version of the C++ API (version 1.0) is in accordance with the AES69-2015 standard. ''' If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://sourceforge.net/p/sofacoustics/code/HEAD/tree/trunk/SOFAlizer/modules/audio_filter/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. c5ee5b94681ae514725146fa6410bee43a0039b5 1983 1982 2015-05-13T13:25:40Z Petibub 4 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/sofa/tree/master/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://github.com/sofacoustics/sofa/tree/master/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://github.com/sofacoustics/sofa/blob/master/SOFAlizer/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. de84a47e24aa449482060eb99e40ad8dc0741b8d 2 480 1986 2015-08-03T10:07:55Z Isfmiho 3 Created page with "<math>E=mc^2</math>" wikitext text/x-wiki <math>E=mc^2</math> c09eb5a37b402a53a3842e454ede6933189ad696 0 15 1987 1983 2015-10-14T15:06:52Z Petibub 4 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://github.com/sofacoustics/sofa/tree/master/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://github.com/sofacoustics/sofa/blob/master/SOFAlizer/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 8fcfe36cbf09e838ee4b3cbcb24faa2e35560f71 1988 1987 2015-10-15T12:30:14Z Petibub 4 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://github.com/sofacoustics/sofa/tree/master/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://github.com/sofacoustics/sofa/blob/master/SOFAlizer/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. a84c9818bdb3a945f51caabf192e6bd218bd3024 1999 1988 2016-09-08T12:23:27Z Petibub 4 SOFAlizer descirpition wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Example of loading SOFA files in C++ == We have a draft [https://github.com/sofacoustics/SOFAlizer source code] for a plug-in called SOFAlizer for the [http://www.videolan.org/vlc/ VLC-Player]. This plug-in is not available within the official release of the VLC-Player yet (but we work on that ;-) ). The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plug-in are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlized-VLC from here, unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 33a5d2620b97744a6cec28c92e171ca487b602dd 2000 1999 2016-09-08T12:29:51Z Petibub 4 /* SOFAlizer: Example of loading SOFA files in C++ */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlized-VLC from [https://github.com/sofacoustics/SOFAlizer/releases here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 6dc6d4a4462166ab01b2b41f10b7080955d9960f 2001 2000 2016-09-08T12:38:24Z Petibub 4 SOFAlizer 0.1.0 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 55a601fc0d4b43213a74710c89bba0bdcdd489ea 2002 2001 2016-09-08T13:10:28Z Petibub 4 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. 4f67b5a394dbbbab68b63e16c3de3c49794f5a21 2018 2002 2017-02-04T17:19:29Z Christian Hoene 917 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/choene/libmysofa Libmysofa] is a light weight C-library to read SOFA files. It hardly has any library dependencies and is suitable for embedded devices. In addition, it normalizes the input data and provides a function to look up and to interpolate the FIR filters for a given orientation. ed84e5e99aa9fe5525eb5d69aaf4a9ab3a801fbd 2019 2018 2017-02-04T17:20:16Z Christian Hoene 917 wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/choene/libmysofa Libmysofa] is a light weight C-library to read SOFA files. It hardly has any library dependencies and is suitable for embedded devices. In addition, it normalizes the input data and provides a function to look up and to interpolate the FIR filters for a given orientation. 192f0b6de029344eca1370adb8624437634c325f 2020 2019 2017-02-10T07:57:28Z Christian Hoene 917 /* libmysofa */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] '''Note:''' * The last stable version 0.4.3 does not fully support the recently published standard AES69-2015. * The full support of AES69-2015 is provided with the version 1.0, which is now in the stage of being a release candidate 2 (1.0RC2). If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library to read SOFA files. It hardly has any library dependencies and is suitable for embedded devices. In addition, it normalizes the input data and provides a function to look up and to interpolate the FIR filters for a given orientation. 65f62ccfb40273d1de9c6fb1498455facddf2bd9 2024 2020 2017-05-24T14:49:18Z Petibub 4 /* API for Matlab/Octave */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library to read SOFA files. It hardly has any library dependencies and is suitable for embedded devices. In addition, it normalizes the input data and provides a function to look up and to interpolate the FIR filters for a given orientation. 850e24520e4d7943b2f8d90eaf9cbfb93c8cb947 2025 2024 2017-05-24T14:49:36Z Petibub 4 /* API for Matlab/Octave */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library to read SOFA files. It hardly has any library dependencies and is suitable for embedded devices. In addition, it normalizes the input data and provides a function to look up and to interpolate the FIR filters for a given orientation. 0f91c8d8faf8d1c321b7c34b752f534dc4a898e5 2026 2025 2017-05-24T14:49:56Z Petibub 4 /* API for C++ */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library to read SOFA files. It hardly has any library dependencies and is suitable for embedded devices. In addition, it normalizes the input data and provides a function to look up and to interpolate the FIR filters for a given orientation. 63e7f990f7405573b3bb2e92d68d286934d4843e 2027 2026 2017-05-24T14:53:25Z Petibub 4 /* libmysofa */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). b28dbda7eeb5f6f47ceeea2cedc73aa85814f500 2030 2027 2017-07-13T12:21:46Z Christian-W. Budde 918 Added WebSofa reference wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as the browser or NodeJS). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo] fda3ea23c8bb802bed72a937610b528d56c4fd7d 2031 2030 2017-07-13T12:58:58Z Christian-W. Budde 918 /* WebSofa */ wikitext text/x-wiki == API for Matlab/Octave == An application-programming interface (API) for Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == SOFAlizer: Demo of a SOFA-based audio engine in C++ == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. == libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo] b8f6330adfd1f4c49f834b7f0fc986e27c531ce7 0 476 1989 1975 2015-11-15T17:11:45Z Petibub 4 /* Description */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is [http://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#SOS_.28proposed.29 SOS], not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note that SimpleFreeFieldSOS 1.0, in contrast to SimpleFreeFieldHRIR 1.0, has not been included in the standard, thus it is declared as stable. Note: * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} 74985a685dea81d1e5ab2d78b8404b196f6b7352 1990 1989 2015-11-15T17:12:57Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is [http://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#SOS_.28proposed.29 SOS], not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note: * In contrast to SimpleFreeFieldHRIR 1.0, SimpleFreeFieldSOS 1.0 has not been included in the standard. But it can be considered as stable. * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} 8f21d2c6b18774c6b5d3007744143b764071bd6d 0 11 1991 1985 2015-11-15T17:25:40Z Petibub 4 formulas edited wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 5bbd5e6a7d5bcf6bb53e8a5eebbb2d5ba1ef442d 0 17 1992 1984 2016-02-01T14:24:38Z Isfmiho 3 updated number of listeners in HRTF database wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. * '''New:''' [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html ff20bf1367ef779b822c4cae982283d92df24123 1995 1992 2016-06-11T19:53:39Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)’' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. * '''New:''' [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 6653590acd1f5f15cccf3250c71dd9eda27a2bc0 1996 1995 2016-06-11T19:54:09Z Petibub 4 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert, Germany)''. * '''New:''' [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html b98bca16e48c05fd9a01126e5948947d8d7db02b 1998 1996 2016-08-16T16:34:56Z Petibub 4 Oldenburg, update from Daryl Kelvasa wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs from the [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Fachhochschule Köln] of the dummy-head Neumann K100. Gapless data, high spatial resolution provided. ''(Credit: Benjamin Bernschütz, Germany).'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * '''New:''' [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 71e54cf70f7271f943f695fe32505394d9f92542 2004 1998 2016-11-21T10:54:56Z Petibub 4 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **'''New: [http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]:''' High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 51b1564e6f475e11adfd9ae38f3de8ad27b0d7a6 2021 2004 2017-05-24T14:21:42Z Petibub 4 TU-Berlin/FABIAN added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** '''New: HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html e623af2329e7c1a0120687490f01f83efb75a113 2022 2021 2017-05-24T14:47:26Z Petibub 4 TU-Berlin/Fabian added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [https://dev.qu.tu-berlin.de/projects/measurements/repository/show/2010-11-kemar-anechoic/mat TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** '''New: HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 80319b3208423080cfe8d61a657a662fa7882f87 2032 2022 2017-07-14T16:02:39Z Hagenw 863 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** '''New: HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html a974d29a9694554a2c0ac0a0117088bd3a446a37 2033 2032 2017-07-19T09:09:36Z Petibub 4 Aachen database added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/Aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF] database, combined with anthropometric data. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** '''New: HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 7c61d9f30e52649c39a91fd1f8c7812239598c18 2034 2033 2017-07-19T10:58:08Z Petibub 4 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * '''New: [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data.''' See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 9ca4396444e9c34b979bf425a89b836c03af2f09 2037 2034 2017-07-21T16:39:54Z Petibub 4 minor change in Aachen wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * '''New: [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners.''' See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 91643e3dd493f8cd2a1a4155de8bc8fd408ed278 2041 2037 2017-11-13T09:05:35Z Petibub 4 SBSBRIRs added. wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * '''New: [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners.''' See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 9183b31962654adb82c093b0858201960690d232 2 481 1993 2016-06-06T08:28:00Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki IT/Programmer at the Acoustics Research Institute, Vienna, Austria d299215f2b5642dcfc4973af2b6928b2d349d68a 3 482 1994 2016-06-06T08:28:02Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 10:28, 6 June 2016 (CEST) 3b65170d4d9c157314e2eaa0bd6933c33d4a1871 0 1 1997 1909 2016-08-16T16:33:51Z Petibub 4 Oldenburg (Kayser2009) update wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Update of the Oldenburg BRIRs (Kayser et al. 2009) for various listening conditions''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 9b53aca78de77dbd26b71f57d4489726578491d9 2003 1997 2016-11-21T10:48:32Z Petibub 4 FH Köln Near-field announced wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 2c84eeb7a4edbb9adbfc640eb049b3fbc66ca48c 2023 2003 2017-05-24T14:48:16Z Petibub 4 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credit: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released d35a831fe1ec4ab420910610fb43d2431916a007 2035 2023 2017-07-19T11:00:18Z Petibub 4 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 19.07.2017: Aachen HRTF database added (Credit: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credit: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credit: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 7bba73a52b499a28976e041a793109fa04fb092e 2036 2035 2017-07-19T11:03:36Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Aachen HRTF database with anthropometric data!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). '''New: WebSofa''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 19.07.2017: Aachen HRTF database added (Credit: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credit: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credit: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credit: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credit: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credit: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credit: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credit: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 4389a9fa90eb4693dae7c8d62021fb71e0a31b16 2 483 2005 2016-12-01T08:47:10Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki Research Fellow at TH Köln 995d1932b382d6a9111d91c0826934289be65709 3 484 2006 2016-12-01T08:47:10Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 09:47, 1 December 2016 (CET) 78f853c8037e8339e0bd147be9fe36f2c4de4c4d 2 485 2007 2017-01-02T08:05:14Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki I have done some research on wireless, voice over ip, and spatial audio. Now I am founder of Symonics GmbH. 8737bea28ee38678ff9d38d13a83927a461aa48a 3 486 2008 2017-01-02T08:05:14Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 09:05, 2 January 2017 (CET) 6a509765cc9f1dba0753618352ebed59a318ac15 2 489 2011 2017-02-02T12:19:41Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki miho test2 miho test2 miho test2 0ced76c13f32674c8b0f05ca541b97bb578666eb 2015 2011 2017-02-02T13:10:09Z Isfmiho 3 Isfmiho moved page [[User:Miho test2]] to [[User:Mihodummy]]: Automatically moved page while merging the user "[[User:Miho test2|Miho test2]]" to "[[User:Mihodummy|Mihodummy]]" wikitext text/x-wiki miho test2 miho test2 miho test2 0ced76c13f32674c8b0f05ca541b97bb578666eb 3 490 2012 2017-02-02T12:19:41Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 13:19, 2 February 2017 (CET) 4168a0cd8cbec6016395786332aa94d8e7769110 2017 2012 2017-02-02T13:10:09Z Isfmiho 3 Isfmiho moved page [[User talk:Miho test2]] to [[User talk:Mihodummy]]: Automatically moved page while merging the user "[[User:Miho test2|Miho test2]]" to "[[User:Mihodummy|Mihodummy]]" wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 13:19, 2 February 2017 (CET) 4168a0cd8cbec6016395786332aa94d8e7769110 2 491 2028 2017-07-13T12:04:13Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki I'm a hobbyist "scientist" experimenting with spatial audio 2e677f8fe485f45dd751cffc5345e09ffb9400e3 3 492 2029 2017-07-13T12:04:13Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 14:04, 13 July 2017 (CEST) 907cca55b0635250bf0ff69224f6f0772abbd5a7 2 493 2038 2017-08-17T06:46:43Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki I am research engineer at VibrasticLab, Dept. of Engineering Physics, ITS Surabaya, Indonesia. 0bbd6fa60a0a9ac347eab6de8fe7f17630399e2d 3 494 2039 2017-08-17T06:46:43Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 08:46, 17 August 2017 (CEST) eac2c1b9a8e2b1202cb9d636c0025b29f9bb6743 0 16 2040 1838 2017-10-19T11:11:57Z Petibub 4 /* Contact */ wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader, Matlab support * '''Markus Noisternig''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Website support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ API, specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): initiation of the [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) * '''Yukio Iwaya''' (Faculty of Engineering, Tohoku Gakuin University) * '''Michele Geronazzo''' (University of Padova): headphone support Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You need to be a member of the mailing list to send a message to the list. You don't need to be a member to send an email to the moderator. Also you are invited to contact the standardization committee of X212. Join us at ([http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. b1da139ce1a3a64e5ce2935891135a543f9d1d59 0 17 2042 2041 2017-11-13T09:07:00Z Petibub 4 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * '''New: [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''' ''(Credit: Chris Pike, Salford)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 0241961a1f4edd402c6418cbce39e3cfb018a60e 2046 2042 2018-05-03T15:54:38Z Hagenw 863 Add SADIE dummy head HRTFs as extzra entry wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/fhk FHK]: HRTFs of the dummy-head Neumann K100 provided by the Fachhochschule Köln: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * '''New: [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''' ''(Credit: Chris Pike, Salford)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 58a297ea821e9257c9d12c8e1dd579ac39cc6a67 2047 2046 2018-05-07T11:18:14Z Petibub 4 Fachhochschule Köln updated to Technische Hochschule Köln wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 120 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK]: HRTFs of the dummy-head Neumann K100 provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * '''New: [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''' ''(Credit: Chris Pike, Salford)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html c8dc78f17d42b4b45fe1a7ca587cf293d0516013 2054 2047 2018-08-24T11:32:24Z Isfmiho 3 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK]: HRTFs of the dummy-head Neumann K100 provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * '''New: [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''' ''(Credit: Chris Pike, Salford)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 85795fb6adf6d082186f383c3145c0482b6c8809 2055 2054 2018-09-05T15:18:56Z Petibub 4 DRIR from THK added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of the dummy-head Neumann K100 provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 481e0aabafb2d1a0a1e99801f323fda962d97bb0 2057 2055 2018-09-05T15:26:41Z Petibub 4 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of the dummy-head Neumann K100 provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * '''New:''' [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * '''New: HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head.''' Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 9eca2e66eccc7d9f8739c28a15d647d3ad354812 2058 2057 2018-09-05T15:27:00Z Petibub 4 /* Headphone impulse responses (HpIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of the dummy-head Neumann K100 provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * '''New:''' [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html e36799f6c54942c2b16bffeed9a0f4631a0a96b2 2059 2058 2018-09-05T15:27:29Z Petibub 4 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b, dtf b: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of the dummy-head Neumann K100 provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * '''New: [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios ''' with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html f16f1be643ea8335bbf2f500d83088c283b98852 0 1 2043 2036 2017-11-13T09:07:57Z Petibub 4 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Aachen HRTF database with anthropometric data!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). '''New: WebSofa''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 7876d73b4490b4d523d4ec258038c1a5393f5ac5 2049 2043 2018-06-11T07:27:27Z Petibub 4 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Aachen HRTF database with anthropometric data!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). '''New: WebSofa''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 1e67b4fcc721462dafe92dbc9353794c2f19938f 2056 2049 2018-09-05T15:25:33Z Petibub 4 DRIR from THK added wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Spatial audio impulse response captured at the WDR broadcast studios provided by the THK ''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). '''New: WebSofa''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released c08ceb7a8e320f7fc08d8f81a07a0e19acf22994 2061 2056 2018-09-06T15:11:35Z Petibub 4 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Spatial audio impulse response captured at the WDR broadcast studios provided by the THK ''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). '''New: WebSofa''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 06.09.2018: SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 0905f735fb7e1ddbb321ce24a3d9043cf3a18d4b 2062 2061 2018-09-06T15:11:54Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Spatial audio impulse response captured at the WDR broadcast studios provided by the THK ''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). '''New: SOFA API for Python (Credits: Jörg Encke, TUM, Munich)''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 06.09.2018: SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 373f4291fd768ee54d80a7a0185ccb9fb0511b8c 2064 2062 2018-09-06T15:14:09Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Spatial audio impulse response captured at the WDR broadcast studios provided by the THK ''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). '''New: pySOFA, a SOFA API for Python (Credits: Jörg Encke, TUM, Munich)''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 04b486329f909a00de3e481f98319f9d54917d89 2 495 2044 2017-11-15T07:37:16Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki I am Abu Jose George Currently a Student at Govt Model Engineering College Thrikkakara.I am intrested in doing a project on Binaural audio using Sofa. f0be6c74d664cbcc87d16bb9e793d5eb29582ade 3 496 2045 2017-11-15T07:37:16Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [[Help:Contents|help pages]]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 08:37, 15 November 2017 (CET) 5a8fb31c9b9ac8c32b9ec210e595f4dbc5998c82 0 15 2048 2031 2018-06-11T07:24:39Z Petibub 4 restructed, dirpat added wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo] == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == DirPat is a tool to analyze and visualize directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. Besides an user interface and signal-processing tools, DirPat provides a database of measured directivities which are handled as SOFA files. More details can found at the [https://opendata.iem.at/projects/dirpat/ DirPat project pages]. 4832aa06dd7c630279e6bde390b18ed2ad17dc38 2050 2048 2018-06-11T07:30:02Z Petibub 4 /* Application: DirPat */ wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo] == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. In order to use SOFAlizer: * Download the official VLC 2.1 from [https://www.videolan.org/vlc/releases/2.1.0.html#download here] and install on your machine * Download the SOFAlizer from [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here], unzip, and copy over your VLC installation * Start VLC * Goto Tools, Preferences, check "Show settings: All" * In the left panel, for Audio/Filters, check "SOFAlizer" * In the left panel, for Audio/Filters/SOFAlizer, select at SOFA file 1,2,3 up to three SOFA files * Click on Save * Goto Tools/Effects and Filters, in that panel, select "SOFAlizer" * Enable SOFAlizer * Load a audio/video file, enjoy The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. bc3c2025cb4713a60dc24a3e5fa899e7dea62573 2051 2050 2018-06-11T07:31:59Z Petibub 4 /* Application: SOFAlizer plug-in for VLC player */ wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo] == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. 8ffb3677c43f420b59efb46a5b0d2b64872f33ea 2052 2051 2018-06-11T07:32:10Z Petibub 4 /* Application: Spat */ wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo] == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. a6f6237c6be51e21dc7047ca1a486c13419f3013 2053 2052 2018-06-11T07:32:18Z Petibub 4 /* API: WebSofa */ wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. 58c8ad7fce72685222a2e116db85998a0db2d1f1 2060 2053 2018-09-06T15:10:32Z Petibub 4 SOFA API for Python added wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: SOFA API for Python == The [https://github.com/Jencke/pySOFA API for Python] is available from Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. f65ee6969aee55ad5727969d6e92331f120afacc 2063 2060 2018-09-06T15:13:24Z Petibub 4 /* API: SOFA API for Python */ wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: SOFA API for Python == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. 145df35ea123ed64f3f76d6922f6e01502dee38b 0 5 2068 1963 2019-02-28T09:30:38Z Fbrinkmann 748 Added Musical Instrument Directivity wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[MusicalInstrumentDirectivity]]: Convention for storing directivity of tonal and a-tonal musical instruments and human singers/talkers. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! b16e2ab2cca80398c8f97c7dd8f3beae2f1ba428 0 497 2069 2019-02-28T10:20:13Z Isfmiho 3 Created page with "This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too gene..." wikitext text/x-wiki This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 907805726b0faa8fcce1e4f499f89097f0dbc53d 2070 2069 2019-02-28T13:48:58Z Fbrinkmann 748 wikitext text/x-wiki This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt' |- |MusicianPosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |MusicianPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||m||E||double||69 = A4 = TuningFrequency |- |EmitterComment||<nowiki>cartesian</nowiki>||m||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)' |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||m||I, E||double||only applicable to tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 138d99556e9445fca4330ba0e6fa0faf752e5889 2071 2070 2019-02-28T13:56:30Z Fbrinkmann 748 wikitext text/x-wiki This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt' |- |MusicianPosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |MusicianPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} fde715ae96216409ce5802b5ed57cc070a27704d 2072 2071 2019-02-28T14:32:33Z Fbrinkmann 748 wikitext text/x-wiki == Description == == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt' |- |MusicianPosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |MusicianPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} a344a81a949c35252ac3f9b18679420f0149c73d 2073 2072 2019-03-26T12:22:09Z Fbrinkmann 748 /* Version 0.1 */ wikitext text/x-wiki == Description == == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt' |- |MusicianPosition||<nowiki>[0 0 1]</nowiki>||m||IC||double|| |- |MusicianPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the musician |- |MusicianView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} f45363a41e9439fe32dbdd37e8e9a74fcc5c27c4 2074 2073 2019-03-26T12:42:12Z Fbrinkmann 748 /* Description */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities for multiple played notes in the frequency domain. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt' |- |MusicianPosition||<nowiki>[0 0 1]</nowiki>||m||IC||double|| |- |MusicianPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the musician |- |MusicianView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 7a4ecd239e9ff67e025e353c55185b7d38428c51 2076 2074 2019-03-26T12:49:03Z Fbrinkmann 748 /* Description */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''Meta data:''' == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt' |- |MusicianPosition||<nowiki>[0 0 1]</nowiki>||m||IC||double|| |- |MusicianPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the musician |- |MusicianView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 9466e4ac0fbbca79b464748205395c73a6912bb1 2077 2076 2019-03-26T13:03:19Z Fbrinkmann 748 /* Description */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (REFERENCE) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt' |- |MusicianPosition||<nowiki>[0 0 1]</nowiki>||m||IC||double|| |- |MusicianPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the musician |- |MusicianView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MusicianUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |MusicianUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |MusicianUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 159ffbbd6701e07aa1ae295f2720b9a45a9db96b 2078 2077 2019-03-26T13:08:47Z Fbrinkmann 748 /* Version 0.1 */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (REFERENCE) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||||||attribute||e.g. 'sitting behind the instrument' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 9625394e25b31f689c2dc61d34858d70a78022d8 2079 2078 2019-03-26T13:16:32Z Fbrinkmann 748 /* Description */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (REFERENCE) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||||||attribute||e.g. 'sitting behind the instrument' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 4fb34a98e6f0031359e4c9da56ba73853a3f629e 2080 2079 2019-03-26T13:18:13Z Fbrinkmann 748 /* Version 0.1 */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (REFERENCE) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} da56fd9f763ed4f1250ca624677fe79b479076b4 2081 2080 2019-03-26T13:20:17Z Fbrinkmann 748 /* Description */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (REFERENCE) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 2a331914b9620524f499ded362d71c3681fe91f1 2082 2081 2019-03-26T13:24:10Z Fbrinkmann 748 /* Version 0.1 */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (REFERENCE) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 5565c3e603f6eeadb38738f3264e96782b50fe29 2083 2082 2019-03-28T11:02:46Z Fbrinkmann 748 wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 3 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} a425d528e0e01ad5ed6366acc840df8fa855df80 2084 2083 2019-04-03T11:24:40Z Fbrinkmann 748 wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 1 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 9f4a15226654c1bd942cea68c143b3de9ee3b7ed 2085 2084 2019-04-03T11:28:51Z Fbrinkmann 748 wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 1 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 1f58aab8de0adda5572588cd49b4c0bce08eb3cb 2086 2085 2019-04-03T11:29:37Z Fbrinkmann 748 wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 1 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} c201056592d7d344cf0ada3c4574419b25a06625 2087 2086 2019-04-03T11:37:16Z Fbrinkmann 748 wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 1 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} c44ab8394745e540abb55a13f2386a957d9d2040 2088 2087 2019-04-03T11:47:16Z Fbrinkmann 748 wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 1 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} a766ce3002dd5f0496c7eeb23d0a2a7584d53fb2 2089 2088 2019-04-03T11:49:08Z Fbrinkmann 748 wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 1 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 5ed5f5bbd91c7399b4ccba12f1e42140ad3ab9e7 2090 2089 2019-04-03T11:49:17Z Fbrinkmann 748 wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 586be365027ff1ae15f3899080d977156eb8510a 2091 2090 2019-04-03T11:55:02Z Fbrinkmann 748 /* Version 0.1 */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||69 = A4 = TuningFrequency. Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 11446d3e253520bd9f552dd62198efbfd841e017 2092 2091 2019-04-03T12:06:56Z Fbrinkmann 748 /* Version 0.1 */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#s4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 3000eb916aa6aab03ab4e9bdbb965e41f14f14b3 2093 2092 2019-04-03T12:07:49Z Fbrinkmann 748 /* Version 0.1 */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterComment||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 11c1106dc68395472d5eddfa5a343e975fd09a94 2094 2093 2019-04-03T12:10:46Z Fbrinkmann 748 /* Version 0.1 */ wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 888cd5a4f059cd1a338a7d6c8196a5659cb2e859 0 459 2075 1968 2019-03-26T12:48:45Z Fbrinkmann 748 /* Description */ wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.1.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 0.2 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Version 0.1, previously proposed as HeadphoneIR (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} 529e42839b7a5d1178d9bf12277259307f7394ac 0 17 2095 2059 2019-05-02T09:29:55Z Isfmiho 3 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of the dummy-head Neumann K100 provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * '''New: [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios ''' with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html f314ebb4534c4b362429f3462fda9c50c09e605f 2144 2095 2019-10-15T06:39:16Z Petibub 4 Head-gear HRTFs added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of the dummy-head Neumann K100 provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs:] Gapless data, high spatial resolution ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs]: High spatial resolution done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs]: High spatial resolution while having various head gears applied ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * '''New: [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios ''' with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 994b81a7129a9783a7a777cee1fe2d42638672f8 0 5 2096 2068 2019-05-10T09:18:01Z Petibub 4 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[MusicalInstrumentDirectivityTF]]: Convention for storing directivity of musical instruments in the frequency domain. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! f8d7fb5a7c08a5be4405d12ad1d6e1445694fc42 2098 2096 2019-05-10T09:37:41Z Petibub 4 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[MusicalInstrumentDirectivityTF]]: Convention for storing directivity of musical instruments in the frequency domain. * [[MusicalInstrumentDirectivity]]: Convention for storing directivity of musical instruments in the frequency domain. First attempt, spatial information in the Source. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 38b1d82e5bbf93ee183dc0e52603b4eb4f4b6684 2099 2098 2019-05-10T09:39:29Z Petibub 4 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[MusicalInstrumentDirectivityTF]]: Convention for storing directivity of musical instruments in the frequency domain. Directivity stored as relation between Source and Listener * [[MusicalInstrumentDirectivity]]: Convention for storing directivity of musical instruments in the frequency domain. First attempt, spatial information in the Source. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 3ede4435c2065942a7a0b34dde58b5f488b59d6d 2124 2099 2019-05-10T19:47:45Z Petibub 4 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[MusicalInstrumentDirectivityTF]]: Convention for storing directivity of musical instruments in the frequency domain. Directivity stored as relation between Source and Listener. Second attempt, actual name FreeFieldDirectivityTF. * [[MusicalInstrumentDirectivity]]: Convention for storing directivity of musical instruments in the frequency domain. First attempt, spatial information in the Source. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! b6908cf04299c39c73adb7d76fbe993680ee3b9e 2125 2124 2019-05-10T19:48:05Z Petibub 4 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[MusicalInstrumentDirectivityTF]]: Convention for storing directivity of musical instruments in the frequency domain. Directivity stored as relation between Source and Listener. Second attempt, current tentative name '''FreeFieldDirectivityTF'''. * [[MusicalInstrumentDirectivity]]: Convention for storing directivity of musical instruments in the frequency domain. First attempt, spatial information in the Source. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! b0220189c9a46c46fd28e435cea22c9e63278631 0 498 2097 2019-05-10T09:18:23Z Petibub 4 renamed from MusicalInstrumentDirectivity wikitext text/x-wiki == Description == This is a convention for storing musical instrument directivities or recordings obtained at multiple receivers and for multiple played notes. The data is saved in the frequency domain and the convention is based on the (not yet existing) GeneralTFE convention. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' ** '''Musical Acoustics:''' The stored data can generally serve research in musical acoustics that is related to the acoustic behaviour of natural sources. ** '''Room acoustical simulation:''' The stored data can be used in room acoustical simulation and auralization and the SOFA convention is intended to establish a common data format for the directivity of natural sources. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 888cd5a4f059cd1a338a7d6c8196a5659cb2e859 2100 2097 2019-05-10T09:50:24Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == This is a convention for storing directivity of musical sources (instruments, loudspeakers, singers, talkers, etc) for multiple musical notes. The data is saved in the frequency domain. The applications can be: ** '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. ** '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. The general setting assumes that a source is surrounded by many microphones which capture the signal emitted by the source from different spatial directions. To this end, the microphones are represented as receivers. * '''Directivity data:''' The instrument is encoded by the source, whereas different notes are encoded by the emitter. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the discrete frequencies specified in Obj.N. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 8b686935329585f446906a62089348fc393dcbdd 2101 2100 2019-05-10T10:09:44Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == This is a convention for storing directivity of musical sources (instruments, loudspeakers, singers, talkers, etc) for multiple musical notes. The data is saved in the frequency domain. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end: * 'Source' represents the acoustic source under consideration. * 'Emitters' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * 'Receivers' represent the microphones capturing the sound from the acoustic source * 'Listener' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * 'MIDINote' describes the note the acoustic source was played. Note that MIDINote can be combined with TuningFrequency for a unique relation between the note and frequency. Both data can be ignored for atonal sources such as loudspeakers. * 'Measurement' captures the modification of the measurement: ** Modified orientation of the microphone array? The ListenerView and ListenerUp will change. ** Another musical note played? The MIDINote will change. * '''Directivity data:''' The signal captured by the Receiver. The data is saved as complex (or real) values in Obj.Data.Real and Obj.Data.Imag at the N discrete frequencies for R receivers and M measurements. ** '''Example 1 - full spectrum:''' The directivity of a cymbal could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case the played notes would refer to different playing styles of the cymbal (different strength or hitting locations). In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). ** '''Example 2 - full spectrum:''' A recording of a violin (single tones, scales, or complete pieces) could be saved as a discrete single sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). The data can be regarded as a raw format from which directivities can be computed. ** '''Example 3 - harmonic spectrum:''' The directivity of a violin could be saved by means of the energy of the fundamental frequency and N-1 overtones of each played note. In this case Obj.Data.N would be of size NE, because the frequencies are different for emitter (each played note). ** '''Example 4 - fractional octave spectrum:''' The directivity of a violin could alternatively be saved as energy in N fractional octaves. In this case Obj.Data.N would be of size N, because the frequencies are identical for each emitter (played note). This format could be most easily used by recent room acoustical simulation algorithms but is not recommended because this simplified representation looses part of the original representation. ** '''Example 5 - moving instrument:''' The influence of the musician on the directivity could be investigated by repeated recordings of the same note/scale/piece for different positions of the musician and/or the instrument. The position can be coded in the meata data. In all other cases the musician and the instrument are ideally not moved during the recording session(s). * '''Meta data:''' The complete description of the provided data unfortunately requires more meta data than in other SOFA conventions. ** '''EmitterPosition:''' Gives a emitting position of each note. In most cases, it won't be possible to specify the position of the emitter, and a null matrix should be given. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} ee492401f8bccfb7bf10a68506183953988d03ce 2102 2101 2019-05-10T10:41:56Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end: * 'Source' represents the acoustic source under consideration. * 'Emitters' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * 'Receivers' represent the microphones capturing the sound from the acoustic source * 'Listener' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * 'MIDINote' describes the note the acoustic source was played. Note that MIDINote can be combined with TuningFrequency for a unique relation between the note and frequency. Both data can be ignored for atonal sources such as loudspeakers. * '''Data:''' The signal captured by a Receiver. The data is saved as complex numbers in Data.Real and Data.Imag at the N discrete frequencies for R receivers and M measurements. * 'Measurement' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 3be2e1d2f9dc938a3ac1181e9a2b258161c1d2f1 2103 2102 2019-05-10T10:42:41Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * 'Source' represents the acoustic source under consideration. * 'Emitters' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * 'Receivers' represent the microphones capturing the sound from the acoustic source * 'Listener' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * 'Data:' The signal captured by a Receiver. The data is saved as complex numbers in Data.Real and Data.Imag at the N discrete frequencies for R receivers and M measurements. * 'MIDINote' describes the note the acoustic source was played. Note that MIDINote can be combined with TuningFrequency for a unique relation between the note and frequency. Both data can be ignored for atonal sources such as loudspeakers. * 'Measurement' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 490eb5d170d731f741d2e6a12ee2a8d371d95195 2104 2103 2019-05-10T10:43:14Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data:''' The signal captured by a Receiver. The data is saved as complex numbers in Data.Real and Data.Imag at the N discrete frequencies for R receivers and M measurements. * '''MIDINote''' describes the note the acoustic source was played. Note that MIDINote can be combined with TuningFrequency for a unique relation between the note and frequency. Both data can be ignored for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. ** '''EmitterMidiNote:''' For tonal instruments, this specifies the midi note number according to (The complete MIDI 1.0 detailed specification (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification) where a note number of 69 refers to A4 (fundamental frequency specified by Obj.TuningFrequency). In case of atonal instruments a null vector should be given. ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} c81b249af4a218c56340978622607dc4ca77b41e 2105 2104 2019-05-10T10:48:15Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data:''' The signal captured by a Receiver. The data is saved as complex numbers in Data.Real and Data.Imag at the N discrete frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was played. For tonal instruments, this specifies the MIDI note (according to [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI 1.0 specification]). Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. ** '''EmitterMidiNote:''' ** '''EmitterComment:''' Gives an additional verbal description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:MusicianPostion:''' Specifies the position of the musician inside the microphone array and relative to the instrument. '''It is recommended that the direction of azimuth 0 deg. and elevation 0 deg. is used as a reference point/virtual audience towards which the musician is oriented.''' ** '''SourceViewDefinition:''' Because there will not be an agreement of how the source view is defined across different instruments, this has to be specified (e.g. 'Viewing direction of the bell' in case of a trumpet) * '''SOFA-API''' ** '''M:''' Number of measurements. Must be M=1. ** '''E:''' Number of emitters, which for example correspond to played notes, or cymbal hits (see examples above). ** '''R:''' Number of receiver, which in this case refers to the number of microphones that were used for recording the data. ** '''N:''' Number of saved frequencies (see examples above). * '''Applications''' == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} ff7b9723a2826569702f5b5c1441cdd0e87d37bd 2106 2105 2019-05-10T11:07:56Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata are supported to more coherent describe the dataset: * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. ** '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. ** '''GLOBAL:SourceViewReference''' provides a narrative description about the spatial reference of the musician, e.g., for the trumpet, 'Viewing direction of the bell'. This may be handy when in referencing across different instruments. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 181d2e1708da1590f39dc290ea9729994c150124 2107 2106 2019-05-10T11:09:11Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata are supported to more coherent describe the dataset: * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription can be provided individually for each Measurement. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. * '''GLOBAL:SourceViewReference''' provides a narrative description about the spatial reference of the musician, e.g., for the trumpet, 'Viewing direction of the bell'. This may be handy when in referencing across different instruments. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 0d87c7a7d4e1c24c28388fe73ed327ea4869675f 2108 2107 2019-05-10T11:12:26Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata are supported to more coherent describe the dataset: * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription can be provided individually for each Measurement. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. * '''SourceView:Reference''' and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the musician, e.g. for the trumpet, 'Viewing direction of the bell' and 'Along the keys, keys up' for SourceView:Reference and SourceUp:Reference, respectively. This may be handy when in referencing across different instruments. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} a070cf9e5870688a160f110886e24946d1da76ab 2109 2108 2019-05-10T11:23:41Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata are supported to more coherent describe the dataset: * <code>NoteDescription</code> provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription can be provided individually for each Measurement. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. * '''SourceView:Reference''' and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the musician, e.g. for the trumpet, 'Viewing direction of the bell' and 'Along the keys, keys up' for SourceView:Reference and SourceUp:Reference, respectively. This may be handy when in referencing across different instruments. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} a4cf535efd55e736dfaa85fe9208fdeee5b503b0 2110 2109 2019-05-10T11:24:16Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata are supported to more coherent describe the dataset: * '''NoteDescription<''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription can be provided individually for each Measurement. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. * '''SourceView:Reference''' and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the musician, e.g. for the trumpet, 'Viewing direction of the bell' and 'Along the keys, keys up' for SourceView:Reference and SourceUp:Reference, respectively. This may be handy when in referencing across different instruments. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 0327e51b387785c71b32d89b415722e31bfcfc0a 2111 2110 2019-05-10T11:24:26Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata are supported to more coherent describe the dataset: * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription can be provided individually for each Measurement. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. * '''SourceView:Reference''' and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the musician, e.g. for the trumpet, 'Viewing direction of the bell' and 'Along the keys, keys up' for SourceView:Reference and SourceUp:Reference, respectively. This may be handy when in referencing across different instruments. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} a070cf9e5870688a160f110886e24946d1da76ab 2112 2111 2019-05-10T11:32:01Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription can be provided individually for each Measurement. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. * '''SourceView:Reference''' and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the musician, e.g. for the trumpet, 'Viewing direction of the bell' and 'Along the keys, keys up' for SourceView:Reference and SourceUp:Reference, respectively. This may be handy when in referencing across different instruments. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} c96783e8e11103b9aa486bd5011e438b31b32e8b 2113 2112 2019-05-10T13:25:11Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription can be provided individually for each Measurement. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the musician, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. This may be handy when in referencing across different instruments. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} f8f9c244b81e6147f82cda4b4cb653f11101e221 2114 2113 2019-05-10T13:27:17Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the musician, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} cdc1c4dcdd3ab8e5c61c0df4b72ec4361ce14c72 2115 2114 2019-05-10T13:28:56Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the standard frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} fce33f2958309717242cf2f3e43f8228bdb8b644 2116 2115 2019-05-10T13:37:49Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''Tuning''' describes the tuning frequency the instrument is tuned to (default: frequency in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 0347be1c8e07c6693be79644ccd569e44a61084f 2117 2116 2019-05-10T13:38:40Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The notes is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 7e8db93978ad6ee5bbd7de18324accfe9a3b166e 2118 2117 2019-05-10T13:40:56Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MusicalInstrumentDirectivity</nowiki>||rm||||attribute||This conventions stores directivities of tonal instruments, atonal instruments, and singers/speakers, i.e., this requires some additional meta data entries. This convention is based on the not existing GeneralTFE. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||e.g. 'Violin' or 'human singer' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||e.g. 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||e.g. 'Christiane Schmidt', or 'artificial excitation by R2D2' |- |GLOBAL:MusicianPosition||<nowiki></nowiki>||m||||attribute||e.g. 'sitting behind the instrument, facing the virtual audience at azimuth 0 deg. and elevation 0 deg.' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourcePosition, e.g., 'Position of the bell' for a trumpet |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceView, e.g., 'Viewing direction of the bell' for a trumpet |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC||double||Gives the orientation of the instrument, singer/speaker |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Definition||<nowiki></nowiki>||m||||attribute||Definition of the SourceUp, e.g., 'Viewing direction of the valves' for a trumpet |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterMidiNote||<nowiki>cartesian</nowiki>||||E||double||Defines the played note, e.g. 69=A4, 70=A#4, etc. (According to 'The complete MIDI 1.0 detailed specification' (version 96.1, third edition), https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |EmitterDescription||<nowiki>cartesian</nowiki>||||S, ES||attribute||verbal description of playing style, e.g., 'played on A string (pianissimo, pizzicato)', Not mandatory but highly recommended. |- |Data.Real||<nowiki>0</nowiki>||m||mREn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MREN||double||The imaginary part of the complex spectrum |- |TuningFrequency||<nowiki></nowiki>||||I, E||double||Defines the fundamental frequency of A4 (midi note number 69). Not mandatory, but highly recommended for tonal instruments and singers |- |TuningFrequency:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |TuningFrequency:Units||<nowiki>hertz</nowiki>||||||attribute||Unit of values given in TuningFrequency |- |N||<nowiki>0</nowiki>||m||N, NE||double||Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 46be931eb890cee86d95ef853cd0e2ec2f1c8dcd 2122 2118 2019-05-10T19:32:08Z Petibub 4 /* Version 0.1 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 7b446533f7e593acd035ad5f5120b553dd23d51f 2123 2122 2019-05-10T19:34:02Z Petibub 4 /* Version 0.1 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 3d8982dea346b90fae7b6b4e74aab877e0ee3f3a 1 499 2119 2019-05-10T14:33:59Z Petibub 4 Created page with "TuningFrequency:LongName: not required, because TuningFrequency is always frequency. TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always...." wikitext text/x-wiki TuningFrequency:LongName: not required, because TuningFrequency is always frequency. TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always. ListenerView/Up: added because required to define the orientation of the microphone array SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same. EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore. EmitterDescription: renamed to MIDINoteDescription because it describes a note. GLOBAL:MusicianPosition: renamed to GLOBAL:Musician To be discussed: * MIDINote (and MIDINoteDescription) '''or''' Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex... d5042cba672055e814c65320e2b1eae611115163 2120 2119 2019-05-10T14:34:40Z Petibub 4 wikitext text/x-wiki changes: * TuningFrequency:LongName: not required, because TuningFrequency is always frequency. * TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always. * ListenerView/Up: added because required to define the orientation of the microphone array * SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same. * EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore. * EmitterDescription: renamed to MIDINoteDescription because it describes a note. * GLOBAL:MusicianPosition: renamed to GLOBAL:Musician To be discussed: * MIDINote (and MIDINoteDescription) '''or''' Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex... 9fddb1581bed1327fbd1c45af66a289a2b38dd5f 2121 2120 2019-05-10T16:39:55Z Petibub 4 wikitext text/x-wiki changes: * TuningFrequency:LongName: not required, because TuningFrequency is always frequency. * TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always. * ListenerView/Up: added because required to define the orientation of the microphone array * SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same. * EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore. * EmitterDescription: renamed to MIDINoteDescription because it describes a note. * GLOBAL:MusicianPosition: renamed to GLOBAL:Musician To be discussed: * MIDINote (and MIDINoteDescription) '''or''' Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex... * Conventions name: if we want to keep it simple, we could ignore the room (the usual case when talking about directivity). Then, the convention could be called FreeFieldDirectivityX, with X={TF|FIR}. Note that I skipped the "MusicalInstrument" because this is limiting and we consider directivity of loudspeakers and singers already now, i.e., more than just instruments. efbc51563e204ad6720c0aeddfca0bf9b1d6d39f 0 15 2126 2063 2019-05-28T11:43:26Z Petibub 4 pysofaconventions added wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: SOFA API for Python == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == API: pysofaconventions for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full convention implementation, taking the C++ API as a reference. It is covered by unit tests, see the [https://coveralls.io/github/andresperezlopez/pysofaconventions?branch=master test coverege statistics]. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. 29cf0cc31c12aee6752494355eac36cff601b3fd 2127 2126 2019-05-28T11:43:51Z Petibub 4 wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: SOFA API for Python == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == API: pysofaconventions for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full convention implementation, taking the C++ API as a reference. It is covered by unit tests, see the [https://coveralls.io/github/andresperezlopez/pysofaconventions?branch=master test coverege statistics]. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. 880937fc6840133718ca7a9bee7958e999510769 2130 2127 2019-05-28T15:58:40Z Petibub 4 wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: pysofaconventions for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full convention implementation, taking the C++ API as a reference. It is covered by unit tests, see the [https://coveralls.io/github/andresperezlopez/pysofaconventions?branch=master test coverege statistics]. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == API: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. d22b9a272c557ef14cda2d2d18e6204cae1f1309 2131 2130 2019-05-28T16:59:32Z Petibub 4 /* API: pysofaconventions for Python */ wikitext text/x-wiki == Generic: HDF5View == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == API: SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == API: SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == API: pysofaconventions for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == API: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == API: libmysofa == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == API: WebSofa == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. c84f8dd797ebaf029ddc61908929caaa8a1ae742 2136 2131 2019-06-18T12:45:37Z Petibub 4 SOFAsonix added wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. e663a6cc3f151dc255e20b2bf604dd79b248af1a 2139 2136 2019-07-04T09:21:53Z Petibub 4 sofa for max added wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libmysofa and enables SOFA files to be utilised in patches designed for spatial audio reproduction. The binaries are available for [https://github.com/APL-Huddersfield/SOFA-for-Max/releases Linux and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. 37dde5db20a2bf48cc52d7b746962b739ae90b69 2141 2139 2019-07-10T12:52:04Z Petibub 4 /* sofa~: SOFA for Max */ wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. a748ec47df80a5be3f5554e44574d18deb31d1e9 0 1 2128 2064 2019-05-28T12:03:05Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. '''New: Spatial audio impulse response captured at the WDR broadcast studios provided by the THK ''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 930859302b4f41bc9a267f6b6ec356db45b5edc8 2129 2128 2019-05-28T12:04:06Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 5db051d0c858bf6dcf9f8c782524b4f254317218 2137 2129 2019-06-18T12:47:16Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: SOFAsonix and pysofaconventions added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 793d843819f3dad2f470ed58c1cb8c7f0d3bcf64 2140 2137 2019-07-04T09:23:39Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: SOFA for Max and SOFAsonix added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 7e2b5af73c27b4d925d2f4cdeff85705a608a336 2 500 2132 2019-06-04T19:35:52Z Ente 1 Creating user page for new user. wikitext text/x-wiki Dr S.China Venkateswarlu is working as a professor in the Department of Electronics and Communication Engineering. He has 21 years of professional experience including 2.6 years in industry, about 19 years in teaching. He obtained his B.Tech (Electronics & Communication Engineering) degree from Acharya Nagarjuna University, Guntur, A.P. M.Tech(Digital Systems & Computer Electronics) from JNTUH, Hyderabad and PhD(Digital Signal Processing) from the JNTUK, Kakinada. In his career in Academia, he has held various positions such as Associate Lecturer, Assistant Professor, Associate Professor, Professor, Dean, Department Head and Principal. He has taught more than 25 Engineering subjects for UG/PG programmes. He is worked in Abroad as an Associate Professor in School of Electrical & Computing Engineering, from Adama Science & Technology University, Adama, Ethiopia. He has published more than 25 papers in National and International journals and conferences. He has reviewed one Book on Digital Signal Processing from M/S Persons Educations. He is a Life member of ISTE, CSI, SDIWC, and IAENG. He is working as a Reviewer in Different International Journals under EDAS. His areas of interest are Digital Signal Processing, Image and Speech Processing. 1. He has published Text Book on “Wavelet Hybrid Threshold and Window Functions for Speech Enhancement” from Lap_LAMBERT Academic Publishing: 978-613-9-89840-40. 2. Award for “Excellence in Research” from EET CRS 3rd South Asian Education Awards-2018 http://educationexpo.tv/southasianeducationawards. 3. Award for “Best Paper Award”, S.China Venkateswarlu, A.Subba Rami Reddy and .K.Satya Prasad Topic on “Speech Enhancement in Terms of Objective Quality Measures with Effect of Adjustable Window Shape Parameters”, from International Journal-WJTER, on December2017.INDIA. http://wjter.com/ . 4. Award for “Best Teacher Award” for Academic Year 2006-07, from CMRCET,Hyderabad. 696cf8f7c9c53fd18db7517a509c1b1cdce30689 3 501 2133 2019-06-04T19:35:52Z Ente 1 Welcome! wikitext text/x-wiki '''Willkommen bei ''Sofaconventions''!''' Wir hoffen, dass du viele gute Informationen beisteuerst. Möglicherweise möchtest du zunächst die [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Ersten Schritte] lesen. Nochmal: Willkommen und viel Spaß! [[User:Ente|Ente]] ([[User talk:Ente|talk]]) 21:35, 4 June 2019 (CEST) 4b634ca587b1549bff5970c5a5acc3fc5eea08af 2 502 2134 2019-06-04T19:36:13Z Ente 1 Creating user page for new user. wikitext text/x-wiki Researcher at MTG/UPF and Eurecat (Barcelona). 85003dd3df4fd954d54228655fb180f07c1e1138 3 503 2135 2019-06-04T19:36:13Z Ente 1 Welcome! wikitext text/x-wiki '''Willkommen bei ''Sofaconventions''!''' Wir hoffen, dass du viele gute Informationen beisteuerst. Möglicherweise möchtest du zunächst die [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Ersten Schritte] lesen. Nochmal: Willkommen und viel Spaß! [[User:Ente|Ente]] ([[User talk:Ente|talk]]) 21:36, 4 June 2019 (CEST) 055a180a7f0953818f9aa5c0855205411c098fc9 6 504 2138 2019-06-26T15:56:23Z Petibub 4 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 2 505 2142 2019-07-22T09:09:39Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki Multi platinum mixing engineer from 1985 to 2004. Currently working in Integrated A/V systems in NYC. Spatial audio, acoustics, 3D Audio was always a passion for me. However the technology was not truly there for many years when I was at the peak of my Engineering Mixes. But that has obviously changed a lot. I always had ideas and concepts but the technology wasn't there. I would really like to find a place back in this field and community. 610a62d484f5f12486d46f7957c8b22e539d9dcf 3 506 2143 2019-07-22T09:09:39Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 11:09, 22 July 2019 (CEST) 7fd2f59db9260bf6df8a2954994735a0f897ea6f 0 1 2145 2140 2019-10-15T06:41:14Z Petibub 4 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: SOFA for Max and SOFAsonix added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released e534e758610b9219f47ba60bc6abf088eec652b9 2146 2145 2019-10-15T06:41:59Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], BRIRs, and DRIRs measured by different researchers. ''' New: HRTFs while wearing head gears added!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: SOFA for Max and SOFAsonix added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released e875404b8d21b2107652df438bfee828594f4a00 2150 2146 2020-01-22T08:48:34Z Petibub 4 widespread added wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. ''' New: PRTFs with pinna meshes, 1005 datasets!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: SOFA for Max and SOFAsonix added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France). * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 45c90e48d89ab1fe21c1e8faa3bbc1887e1588b9 2151 2150 2020-01-22T08:49:04Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. ''' New: Widespread: PRTFs with pinna meshes of 1005 ears!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: SOFA for Max and SOFAsonix added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France). * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 02b8c91c1555a50a2eb495122cf2f5c1ce1dfd53 2166 2151 2020-04-07T11:33:38Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. ''' New: Widespread: PRTFs with pinna meshes of 1005 ears!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: 3D Tune-In Toolkit and Anaglyph added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France). * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 4abc61679bd9a64e8f2adc3cd1730a1bf1d52d60 2186 2166 2020-06-04T14:06:22Z Petibub 4 Chedar added wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. ''' New: Widespread: PRTFs with pinna meshes of 1005 ears!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: 3D Tune-In Toolkit and Anaglyph added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France). * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released b7a642e9071fe46b09b44197c778c10f2aad651a 2187 2186 2020-06-04T14:06:56Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or directional room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, DRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. ''' New: CHEDAR: Numerically calculated HRTFs (with 3D meshes provided)!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: 3D Tune-In Toolkit and Anaglyph added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France). * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 2bfa3231e37d44332053c5c574d94c906545a5a4 0 17 2147 2144 2019-10-15T06:50:30Z Petibub 4 /* General purpose database: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * '''New: [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios ''' with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 9297c37a87fb9c2f0ed3a1153e6c85e8fd374258 2148 2147 2020-01-22T08:43:11Z Petibub 4 widespread added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread WideSpread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the [http://sofacoustics.org/data/database/widespread/Widespread2020.pdf documentation] and upcoming publication. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == '''New: HpIRs of humans: ''' * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database provided. 16 Listeners, 3 headphones ''(Credit: Michele Geronazzo, Italy)''. * HpIRs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)'' == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html b0e2ad29246afa4a9e7795b6f47aef9445decdf9 2149 2148 2020-01-22T08:44:56Z Petibub 4 /* Headphone impulse responses (HpIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database]: == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread WideSpread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the [http://sofacoustics.org/data/database/widespread/Widespread2020.pdf documentation] and upcoming publication. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose: == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 5b18ef9dea46073e4b1150ff59cd21abeb62aa3f 2152 2149 2020-01-22T08:50:45Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database HRTFs, PRTFs, and DRIRs] == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread WideSpread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the [http://sofacoustics.org/data/database/widespread/Widespread2020.pdf documentation] and upcoming publication. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 1b15eeb482fb9519e1f00f477406d4ddc8a0843b 2153 2152 2020-01-22T08:51:22Z Petibub 4 /* General purpose HRTFs, PRTFs, and DRIRs */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread WideSpread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the [http://sofacoustics.org/data/database/widespread/Widespread2020.pdf documentation] and upcoming publication. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 7cad872b8f94fff87acbdc26d76f9875f532d71b 2154 2153 2020-01-22T08:54:06Z Petibub 4 /* General purpose database (HRTFs, PRTFs, and DRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread WideSpread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the [http://sofacoustics.org/data/database/widespread/Widespread.pdf documentation] and upcoming publication. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html ef58b0802cfa12e2f6700507fcbe68edf855d5e0 2155 2154 2020-01-22T08:55:43Z Petibub 4 /* General purpose database (HRTFs, PRTFs, and DRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the [http://sofacoustics.org/data/database/widespread/Widespread.pdf documentation] and upcoming publication. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 4bc75c71ebf7070338dfa2e9158c5f516eccc5df 2156 2155 2020-01-27T10:18:11Z Petibub 4 bug fix in PRTFs wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (preprint)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 65dce8a92b38af0966ed5c93b757d0b0b43dcafd 2157 2156 2020-01-28T11:54:56Z Fbrinkmann 748 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS]: HRTFs from the [https://doi.org/10.17743/jaes.2019.0024 HUTUBS] database containing anthropomeric data, hedphone impulse responses, and 3D head models from 96 listeners. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (preprint)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 8e3e71919dc569b658482580b04996e61a5dfd7a 2158 2157 2020-01-28T11:56:28Z Fbrinkmann 748 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (preprint)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html da48c1132bf972a1e7ec9a12b59b94f061fd6c7d 2159 2158 2020-03-18T12:34:26Z Petibub 4 /* General purpose database (HRTFs, PRTFs, and DRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://www.york.ac.uk/sadie-project/binaural.html SADIE]: Far-field HRTFs from the [http://www.york.ac.uk/sadie-project/binaural.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/binaural.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 70cf1eee0810d1d76138f9888487ec3173d97f52 2160 2159 2020-03-20T10:27:01Z Isfmiho 3 links for SADIE database fixed wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/database.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 5b35b849a5fae05c2476703fd4e38153f01c0f29 2161 2160 2020-03-20T10:28:54Z Isfmiho 3 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [https://www.york.ac.uk/sadie-project/ SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/database.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/database.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html c3dac012d37e3572095ce40902a6f32300616a17 2168 2161 2020-04-28T09:11:12Z Petibub 4 /* General purpose database (HRTFs, PRTFs, and DRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [https://www.york.ac.uk/sadie-project/ SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/database.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/database.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 256b4b7a1d10122c15143de6fb2cd8e72e565d1e 2169 2168 2020-04-28T09:11:44Z Petibub 4 /* General purpose database (HRTFs, PRTFs, and DRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [https://www.york.ac.uk/sadie-project/ SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/database.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [https://www.york.ac.uk/sadie-project/database.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html 5ac2f3856496081c4bcd759cd4bce99e09607c5d 2170 2169 2020-04-28T09:17:15Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/ SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/database.html SADIE] database of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' * [https://www.york.ac.uk/sadie-project/database.html SADIE]: HRTFs measured on a [https://www.york.ac.uk/sadie-project/Measurementconfig.html#Dummyheadang sphere] at a distance of 1.5 m with a KEMAR and a Neumann dummy head. ''(Credit: Gavin Kearney, York)'' b6fc9e095a92121d7bbf0a0cff2d5075bb437f47 2171 2170 2020-04-28T09:18:20Z Petibub 4 /* Other repositories */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 170 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 640644514d08ec2f7fce7ffd1657c82cc39da13b 2184 2171 2020-05-25T06:07:51Z Isfmiho 3 /* number of subjects updated */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' eb5c21bbc20165799d6d1d46b690f3af6d4b5109 2185 2184 2020-06-04T14:05:39Z Petibub 4 Chedar added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100 ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 57f2fe6717df79cea8cf1e2ba51957b469d3c71d 2189 2185 2020-07-16T15:23:36Z Petibub 4 clarification of files in thk wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_*]: DRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 1c1fce6532687f94a0e471348f0a3ae5a5330bc0 2190 2189 2020-07-16T15:26:10Z Petibub 4 /* General purpose database (HRTFs, PRTFs, and DRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 2f047fdca85d33c865c5cf902cac928056a5f087 0 10 2162 124 2020-03-28T10:42:23Z Petibub 4 /* Typical measurement setups */ wikitext text/x-wiki == General == [http://en.wikipedia.org/wiki/Head-related_transfer_function Head-related transfer functions (HRTFs)] describe the spatial filtering of the incoming sound due to the listener's anatomy. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are crucially important for the binaural reproduction of virtual acoustics. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] but also more complex data, e.g., [http://en.wikipedia.org/wiki/Impulse_response directional room impulse responses] (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were those of a [http://en.wikipedia.org/wiki/Dummy_head_recording dummy-head] microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are provided as [http://en.wikipedia.org/wiki/Impulse_response impulse responses (IRs)] with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIR databases have been made publicly available [3–8]⁠. All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1 from [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download here]). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement setups use only two microphones to record the left and right ear signals. However, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1 from [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download here]. The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] file format should thus consider even such parameters. == Aim of SOFA == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an [http://en.wikipedia.org/wiki/Impulse_response impulse response, IR]) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] corresponds to a predefined direction used in the measurements. While the representation of [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] matrix and additional matrices describing the direction of the corresponding [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF], thus, allowing to represent [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from any direction. In that formats, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from each listener are stored in a separate file. In the database storing the [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] , allowing to store [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 2739b251a41d6bf5a6bf299c83250c7165eb25b2 0 9 2163 1966 2020-03-30T08:10:09Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.4, we use SourcePosition to represent the different HRTF directions. By doing so, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the last version before AES69-2015, we adapted the conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). SimpleFreeFieldHRIR version 1.0 represents the current standardized convention set from AES69-2015. == Version 1.0 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This convention set essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This convention set can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 H 0; 0 -H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRIR</nowiki>||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Version 0.4 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 517ee31f516c7aa6ab98607cd0fa493334237bb5 0 15 2164 2141 2020-04-07T07:44:09Z Petibub 4 3D Tune-In Toolkit added wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization and simulation using headphones developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. cb33dd8395edf7d801b3ae56511c1f9dec087cad 2165 2164 2020-04-07T11:27:34Z Petibub 4 Anaglyph added wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. a2171c998b13c0e9d3dc9cb53a1a6d35c69cb1e0 0 498 2167 2123 2020-04-21T08:53:19Z Fbrinkmann 748 wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 7079b08f515de45cc7292cd4b9ad52e86a0ee4bf 2175 2167 2020-05-04T15:52:09Z Petibub 4 Reverted edits by [[Special:Contributions/Fbrinkmann|Fbrinkmann]] ([[User talk:Fbrinkmann|talk]]) to last revision by [[User:Petibub|Petibub]] wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''NoteDescription''' provides a narrative description of each note, which is highly recommend for documenting the data. This might be the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 3d8982dea346b90fae7b6b4e74aab877e0ee3f3a 2176 2175 2020-05-04T15:53:10Z Petibub 4 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 9354b815280ea6a7cc3bbac677207ea9504b698f 2177 2176 2020-05-04T16:01:04Z Petibub 4 v0.2 wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data), e.g., the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} ca816d037830b3d0817bddac576bffa74354cee3 2178 2177 2020-05-04T16:01:21Z Petibub 4 /* Version 0.2 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data), e.g., the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} f57faf0101c7e38fe988010e24457fe54e12a4c5 2179 2178 2020-05-04T16:03:57Z Petibub 4 Petibub moved page [[MusicalInstrumentDirectivityTF]] to [[FreeFieldDirectivityTF]]: was MusicalInstrumentDirectivityTF previously wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). Examples for the data representation: * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data), e.g., the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} f57faf0101c7e38fe988010e24457fe54e12a4c5 2188 2179 2020-07-07T10:38:14Z Fbrinkmann 748 wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Combined directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured together. In this case, the number of emitters should be e=2. The number of measurements is most likely m=1. It could have other values, for example if the directivity is specified for different input levels, which can be specified in Description. * '''Two-way loudspeaker:''' Separate directivities of the low-frequency unit (emitter) and mid/high-frequency unit (emitter) of a loudspeaker. In this case the number of emitters and measurements should be '''e=m=2'''. Although it is possible to have multiple measurements for each emitter, this is not recommended. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data), e.g., the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} b2ec295a6c7c4ed887f1740b071727724efc2005 2191 2188 2020-07-28T15:17:56Z Fbrinkmann 748 changes according to the proposed Version 1 in AES69 wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Harmonic spectrum:''' The directivity of a violin, saved for each harmonic frequency beginning with the fundamental frequency and ending at (N-1)th overtone of each played note. Data.N represents the index to a harmonic frequency with respect to the fundamental frequency described by MIDINote and TuningFrequency. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Combined directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured together. In this case, the number of emitters should be e=2. The number of measurements is most likely m=1. It could have other values, for example if the directivity is specified for different input levels, which can be specified in Description. * '''Two-way loudspeaker:''' Separate directivities of the low-frequency unit (emitter) and mid/high-frequency unit (emitter) of a loudspeaker. In this case the number of emitters and measurements should be '''e=m=2'''. Although it is possible to have multiple measurements for each emitter, this is not recommended. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, ES||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 04227fdac20a6ca5b0fbb785db3e36c33d54df99 2192 2191 2020-07-28T16:07:58Z Fbrinkmann 748 removed incompatible use case wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Combined directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured together. In this case, the number of emitters should be e=2. The number of measurements is most likely m=1. It could have other values, for example if the directivity is specified for different input levels, which can be specified in Description. * '''Two-way loudspeaker:''' Separate directivities of the low-frequency unit (emitter) and mid/high-frequency unit (emitter) of a loudspeaker. In this case the number of emitters and measurements should be '''e=m=2'''. Although it is possible to have multiple measurements for each emitter, this is not recommended. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, ES||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} adbdb14b9f96cf52cfbba39101f967fede8fe573 2193 2192 2020-07-31T15:00:28Z Fbrinkmann 748 changed dimensions of EmitterDescription and EmitterPosition (we now alow only one emitter) wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' represent a more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Combined directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured together. In this case, the number of emitters should be e=2. The number of measurements is most likely m=1. It could have other values, for example if the directivity is specified for different input levels, which can be specified in Description. * '''Two-way loudspeaker:''' Separate directivities of the low-frequency unit (emitter) and mid/high-frequency unit (emitter) of a loudspeaker. In this case the number of emitters and measurements should be '''e=m=2'''. Although it is possible to have multiple measurements for each emitter, this is not recommended. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 8c9c0b484ec735ba266b9d7f7a8c41fd0ae8ede1 2194 2193 2020-07-31T15:07:06Z Fbrinkmann 748 wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 7da51e7e4423930803eca1319b31c537c203d2a0 0 459 2173 2075 2020-04-28T11:33:01Z Petibub 4 Figure updated to Version 0.2 wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.2.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 0.2 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Version 0.1, previously proposed as HeadphoneIR (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} 4805c02e5c775b98c09feb3ca5f12af0c2369756 6 508 2174 2020-04-28T11:44:15Z Petibub 4 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 509 2180 2020-05-04T16:03:57Z Petibub 4 Petibub moved page [[MusicalInstrumentDirectivityTF]] to [[FreeFieldDirectivityTF]]: was MusicalInstrumentDirectivityTF previously wikitext text/x-wiki #REDIRECT [[FreeFieldDirectivityTF]] d174947936036f09b4083d53183a0ec505977cc9 1 499 2181 2121 2020-05-04T16:03:58Z Petibub 4 Petibub moved page [[Talk:MusicalInstrumentDirectivityTF]] to [[Talk:FreeFieldDirectivityTF]]: was MusicalInstrumentDirectivityTF previously wikitext text/x-wiki changes: * TuningFrequency:LongName: not required, because TuningFrequency is always frequency. * TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always. * ListenerView/Up: added because required to define the orientation of the microphone array * SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same. * EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore. * EmitterDescription: renamed to MIDINoteDescription because it describes a note. * GLOBAL:MusicianPosition: renamed to GLOBAL:Musician To be discussed: * MIDINote (and MIDINoteDescription) '''or''' Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex... * Conventions name: if we want to keep it simple, we could ignore the room (the usual case when talking about directivity). Then, the convention could be called FreeFieldDirectivityX, with X={TF|FIR}. Note that I skipped the "MusicalInstrument" because this is limiting and we consider directivity of loudspeakers and singers already now, i.e., more than just instruments. efbc51563e204ad6720c0aeddfca0bf9b1d6d39f 1 510 2182 2020-05-04T16:03:58Z Petibub 4 Petibub moved page [[Talk:MusicalInstrumentDirectivityTF]] to [[Talk:FreeFieldDirectivityTF]]: was MusicalInstrumentDirectivityTF previously wikitext text/x-wiki #REDIRECT [[Talk:FreeFieldDirectivityTF]] 93e22581536cff7d7d174274526161fe8d6bdaa8 0 5 2183 2125 2020-05-04T16:04:44Z Petibub 4 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[FreeFieldDirectivityTF]]: Convention for storing directivity of musical instruments in the frequency domain. Directivity stored as relation between Source and Listener. (It was previously MusicalInstrumentDirectivityTF). * [[MusicalInstrumentDirectivity]]: Convention for storing directivity of musical instruments in the frequency domain. First attempt, spatial information in the Source. * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! ecb0ff186eaaf02cc3365edd869d463a925f0490 0 16 2195 2040 2020-08-03T06:03:03Z Isfmiho 3 personal link added for Markus Noisternig wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader, Matlab support * '''[https://www.noisternig.com/ Markus Noisternig]''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Website support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ API, specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): initiation of the [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) * '''Yukio Iwaya''' (Faculty of Engineering, Tohoku Gakuin University) * '''Michele Geronazzo''' (University of Padova): headphone support Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You need to be a member of the mailing list to send a message to the list. You don't need to be a member to send an email to the moderator. Also you are invited to contact the standardization committee of X212. Join us at ([http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. 8fb1ebe6badd5db7c5ea55f4284a965b277f17db 0 16 2196 2195 2020-08-03T06:06:35Z Isfmiho 3 opening bracket removed (no closing bracket) wikitext text/x-wiki * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=56:di-piotr-majdak&catid=13&Itemid=419 Piotr Majdak]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader, Matlab support * '''[https://www.noisternig.com/ Markus Noisternig]''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[http://www.aipa.tu-berlin.de/menue/team/hagen_wierstorf/parameter/en/ Hagen Wierstorf]''' ([http://www.t-labs.tu-berlin.de/ Telekom Innovation Laboratories], [http://www.tu-berlin.de/ Technical University of Berlin]): Octave support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=293:mihocic-di-fh-michael&catid=13&Itemid=419 Michael Mihocic]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Website support * '''[http://www.kfs.oeaw.ac.at/index.php?option=com_content&view=article&id=665:ziegelwanger-dipl-ing-harald&catid=13&Itemid=419 Harald Ziegelwanger]''' ([http://www.kfs.oeaw.ac.at Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ API, specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): initiation of the [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) * '''Yukio Iwaya''' (Faculty of Engineering, Tohoku Gakuin University) * '''Michele Geronazzo''' (University of Padova): headphone support Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You need to be a member of the mailing list to send a message to the list. You don't need to be a member to send an email to the moderator. Also you are invited to contact the standardization committee of X212. Join us at [http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. afc693af329f7a25ec3e3ade4909e84cdc94a4ac 3 512 2198 2020-08-03T08:48:35Z Ente 1 Welcome! wikitext text/x-wiki '''Willkommen bei ''Sofaconventions''!''' Wir hoffen, dass du viele gute Informationen beisteuerst. Möglicherweise möchtest du zunächst die [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Ersten Schritte] lesen. Nochmal: Willkommen und viel Spaß! [[User:Ente|Ente]] ([[User talk:Ente|talk]]) 10:48, 3 August 2020 (CEST) 994ab14a36dbefd6c1aa83dcf299891f007c67b3 2 515 2201 2020-08-03T09:26:44Z Ente 1 Created page with "Ducks Rule." wikitext text/x-wiki Ducks Rule. 654c364b926c90940b3b5b5b6a1446d11037f4f2 2202 2201 2020-08-03T09:27:15Z Ente 1 wikitext text/x-wiki Ducks Rule. [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] f59c4684a76f2a5f6c80fe28384d7f3595bd2d24 2204 2202 2020-08-03T09:29:12Z Ente 1 wikitext text/x-wiki Ducks Rule. [[File:Scary goose.jpg]] 9b999eac84dae4513b5d614555294ab7a1108529 2205 2204 2020-08-03T09:50:00Z Ente 1 wikitext text/x-wiki Ducks Rule. [[File:Scary goose.jpg]] [[File:testmiho.png]] e03af9bf58f29334373d65bbe43c7e012f0dee22 2206 2205 2020-08-03T09:50:08Z Ente 1 wikitext text/x-wiki Ducks Rule. [[File:Scary goose.jpg]] 9b999eac84dae4513b5d614555294ab7a1108529 2209 2206 2020-08-03T21:50:14Z Ente 1 Ein Bild sagt mehr als tausend Worte. wikitext text/x-wiki [[File:Scary goose.jpg]] 894a1fe42fc794ed375fab8181ff143aa8bff7a2 6 516 2203 2020-08-03T09:28:52Z Ente 1 https://commons.wikimedia.org/wiki/File:Scary_goose.jpg Transferred from en.wikipedia to Commons by Maksim. The original description page was here. All following user names refer to en.wikipedia. Goose. Photo by sannse. wikitext text/x-wiki == Summary == https://commons.wikimedia.org/wiki/File:Scary_goose.jpg Transferred from en.wikipedia to Commons by Maksim. The original description page was here. All following user names refer to en.wikipedia. Goose. Photo by sannse. 76f33118a0c97075df14b15368f14f119936658d 2 517 2207 2020-08-03T13:34:45Z Ente 1 Creating user page for new user. wikitext text/x-wiki Damit ich es nicht nur mit einem (bzw. zwei) Konten getestet habe, muss ich leider noch ein weiteres Konto anlegen. 6b59bed6922b927d2665215ba50ff68ac9caf70e 2210 2207 2020-08-03T22:17:39Z Erpelstolz 955 wikitext text/x-wiki Testkonto zum Test des Mediawiki-Updates. b325549a09d8ed02b7d9f4d8f70e7a0f95333617 3 518 2208 2020-08-03T13:34:45Z Ente 1 Welcome! wikitext text/x-wiki '''Willkommen bei ''Sofaconventions''!''' Wir hoffen, dass du viele gute Informationen beisteuerst. Möglicherweise möchtest du zunächst die [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Ersten Schritte] lesen. Nochmal: Willkommen und viel Spaß! [[User:Ente|Ente]] ([[User talk:Ente|talk]]) 15:34, 3 August 2020 (CEST) 5a45154e5f7f515045482cadb9a0843106bee7e4 0 11 2211 1991 2020-08-04T05:58:59Z Isfmiho 3 test image wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] [[File:mihoart.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 31e22b5c50cbd1e8311577edda891c346826fc67 2212 2211 2020-08-04T05:59:12Z Isfmiho 3 test image removed wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === FIRE (proposed) === FIRE is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 995308e0dc3e3276e22112a3826991dfa4a58ce8 2222 2212 2020-08-04T16:45:54Z Petibub 4 FIR-E added, deprecated FIRE. wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (proposed) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 1f81a1f5bd40d93f687045bd0180fde685ef3075 2223 2222 2020-08-04T16:46:03Z Petibub 4 /* SOS (proposed) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 4cad9355654ce14b1d18735a7f38f2715267e5bd 2224 2223 2020-08-04T16:46:18Z Petibub 4 /* TF (SOFA 1.0) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 30fa0ae478276373e4e9d7a451a44ddbf3360759 2225 2224 2020-08-04T16:46:25Z Petibub 4 /* FIR (SOFA 1.0) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 7e5605d09850ad71acc0b3b4d1a94f67d770c9d3 2226 2225 2020-08-04T16:46:42Z Petibub 4 /* SOS (SOFA 1.1) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} af18785b93a018b8b755e715995a203c3c18107b 2227 2226 2020-08-04T16:46:58Z Petibub 4 /* FIRE (deprecated) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == [[file:Coordinate_system.png]] == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 090fffc27cddff3c37b33ae58f0ac76476b1297a 2231 2227 2020-09-05T15:29:54Z Petibub 4 Spherical harmonics added wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 1.1 adds a spatially ''continuous'' representation of receivers (and emitters) by means of spherical harmonics. To this end, data depending on the position of the receivers (and emitters) are stored as real-valued spherical harmonic coefficients along the dimension R (and E, respectively). Thus, each subset of data for a specific R (and E, respectively) corresponds not to a specific receiver (and emitter, respectively) position, but to a specific spherical harmonic order and degree. Along the dimension R (and E, respectively), the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 23cc1c532699becd14d6c9c1bef883ab18b1fdec 2232 2231 2020-09-05T15:38:31Z Petibub 4 /* Coordinate system */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 1.1 adds a spatially ''continuous'' representation of receivers by means of spherical harmonics. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Harmonic' and ReceiverPosition_Units of 'Spherical'. As the directional information is stored in the data, ReceiverPosition contains information about the radius represented in the spherical coordinate system of SOFA 1.0. SOFA 1.1 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 95908fb6a312cdaf402a8cf7d3bd04d4d0054e0e 2233 2232 2020-09-07T14:48:17Z Petibub 4 /* Coordinate system */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 1.1 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Harmonic' and ReceiverPosition_Units of 'Spherical'. As the directional information is stored in the data, ReceiverPosition contains information about the radius represented in the spherical coordinate system of SOFA 1.0. SOFA 1.1 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} e93055bc5f9b210b8393c15cd87738159fd9b887 2234 2233 2020-09-07T14:49:53Z Petibub 4 /* Coordinate system */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 1.1 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 1.1 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 7816c71a9740d435e1bb6735e9afd82f20338ba1 2236 2234 2020-09-18T16:05:23Z Petibub 4 /* Coordinate system */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 1.1) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 1.1) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 94f105b6ec3ea91b3e8e26647f07db389db01ce5 2237 2236 2020-09-18T16:05:48Z Petibub 4 wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 2.0) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 2.0) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 9edd43f08e1331649db6164cfa604b562b1ec39d 6 519 2213 2020-08-04T06:03:58Z Isfmiho 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 498 2214 2194 2020-08-04T08:51:13Z Petibub 4 Petibub moved page [[FreeFieldDirectivityTF]] to [[SimpleFreeFieldDirectivityTF]] wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 7da51e7e4423930803eca1319b31c537c203d2a0 1 499 2216 2181 2020-08-04T08:51:13Z Petibub 4 Petibub moved page [[Talk:FreeFieldDirectivityTF]] to [[Talk:SimpleFreeFieldDirectivityTF]] wikitext text/x-wiki changes: * TuningFrequency:LongName: not required, because TuningFrequency is always frequency. * TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always. * ListenerView/Up: added because required to define the orientation of the microphone array * SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same. * EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore. * EmitterDescription: renamed to MIDINoteDescription because it describes a note. * GLOBAL:MusicianPosition: renamed to GLOBAL:Musician To be discussed: * MIDINote (and MIDINoteDescription) '''or''' Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex... * Conventions name: if we want to keep it simple, we could ignore the room (the usual case when talking about directivity). Then, the convention could be called FreeFieldDirectivityX, with X={TF|FIR}. Note that I skipped the "MusicalInstrument" because this is limiting and we consider directivity of loudspeakers and singers already now, i.e., more than just instruments. efbc51563e204ad6720c0aeddfca0bf9b1d6d39f 0 5 2218 2183 2020-08-04T08:52:09Z Petibub 4 FreeFieldDirectivityTF renamed to SimpleFreeFieldDirectivityTF wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015, we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivity of musical instruments in the frequency domain. Directivity stored as relation between Source and Listener. (It was previously FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF). * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! bea6cc7202b1e0ccf86a33affc63684fe77e620b 2220 2218 2020-08-04T16:25:15Z Petibub 4 New soonish standardized conventions added wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2015 (SOFA 1.1), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[SHFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRTF, the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed SingleRoomDRIR. * [[SingleRoomMIMOIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralFIRE]]: General convention with FIRE as DataType (no restrictions but DataType). * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. * [[SimpleFreeFieldTF]]: as SimpleFreeFieldHRIR, but uses TF as DataType covering special needs coming from HRTF simulations. * [[SimpleFreeFieldSOS]]: as SimpleFreeFieldHRIR, but uses SOS as DataType (second-order sections) covering special needs coming from HRTF rendering. * [[SingleRoomDRIR]]: directional room impulse responses (DRIRs) measured with an arbitrary number of ''receivers'' (such as a microphone array) and an omnidirectional source in a single room. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are currently being discussed. We consider following rules for new SOFA conventions: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available The following SOFA conventions are being discussed. Measured data exist but their description must be fixed in order to create publicly available SOFA files and corresponding software interfaces. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivity of musical instruments in the frequency domain. Directivity stored as relation between Source and Listener. (It was previously FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF). * [[SimpleBRIR]]: Binaural room impulse responses measured with an omnidirectional source in a single reverberant space. Somebody wanted to have this, but the work stopped at the moment. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 052972c0b6740c900b2cd83112686ec496176bd7 2221 2220 2020-08-04T16:39:19Z Petibub 4 deprecated conventions added wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2015 (SOFA 1.1), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[SHFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRTF, the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed SingleRoomDRIR. * [[SingleRoomMIMOIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 720149fd28738f9e041d7e99f0811cef4ec08e5e 2228 2221 2020-08-04T16:48:05Z Petibub 4 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 1.1), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[SHFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRTF, the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed SingleRoomDRIR. * [[SingleRoomMIMOIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 0a6b4e2bacf50a432889120955c6d40aa363dad8 2235 2228 2020-09-10T11:25:49Z Petibub 4 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 1.1), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[SHFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRTF, the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 7c0554a6d30627602282f8a90284977e7e2a7a21 2238 2235 2020-09-18T16:06:08Z Petibub 4 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[SHFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRTF, the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 40bedb7d475c5e777e0a6b5d10f2da636f08cb03 4 22 2219 100 2020-08-04T12:05:50Z Ente 1 formatiert wikitext text/x-wiki ;Website Owner :The Acoustics Research Institute of the Austrian Academy of Sciences : Wohllebengasse 12-14<br /> : A-1040 Vienna, Austria ; a research institute of the :Austrian Academy of Sciences<br /> :Legal entity under the special protection of the Federal Republic of Austria (BGBl 569/1921 idF BGBl I 130/2003)<br /> :Dr. Ignaz Seipel-Platz 2, 1010 Vienna, Austria This website informs about the scientific activities of the Austrian Academy of Sciences, thus following the mission of the Academy to promote the sciences and humanities in every respect and in every field. d1ade675dee2b773a452fb4386bfae908150a867 2 522 2229 2020-08-11T11:45:16Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki I am a Digital Audio Engineering MSc student at the University of West London. I am currently researching methods of approximating/calibrating HRTFs locally on mobile devices and I am currently creating an app that attempts to do this with AR motion tracking. 6cd89118fcbca0f9a950777c5c0eea6d9a1c92f6 3 523 2230 2020-08-11T11:45:16Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 13:45, 11 August 2020 (CEST) 835f401fe2174cf28efc14aed72f1b339fa6ba88 0 1 2239 2187 2020-09-18T16:06:34Z Petibub 4 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. ''' New: CHEDAR: Numerically calculated HRTFs (with 3D meshes provided)!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: 3D Tune-In Toolkit and Anaglyph added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France). * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 8045d82b21cefede7ca77874c7f6c5ef8272a8ac 2 524 2240 2020-10-13T13:14:26Z Petibub 4 Creating user page for new user. wikitext text/x-wiki Acoustical Engineering undergrad at UFSM - Brazil af6b83ce09b948d2bec47c0a8c5837271015a671 3 525 2241 2020-10-13T13:14:26Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 15:14, 13 October 2020 (CEST) 9d0c0bad19a1d52ced3a6f56f9f78246d759db75 1 463 2242 1744 2020-10-28T04:41:33Z Davicarvalho 957 /* 3D3A LAB Database */ new section wikitext text/x-wiki == 3D3A LAB Database == Hello! Is there a specific reason the 3D3A LAB Database is not present in the SOFA repository? here is a link to the dataset: https://www.princeton.edu/3D3A/HRTFMeasurements.html I hope I'm using this tool correctly. Best, c1a7cbca1dc289d062e2a94745d4f5c5e29e9b3d 6 526 2243 2020-10-30T06:54:38Z Isfmiho 3 Typical HRTF/DRIR measurement setup wikitext text/x-wiki == Summary == Typical HRTF/DRIR measurement setup f55a6d4cbdcc56715e886a2915d6215cf3a75fd7 0 10 2244 2162 2020-10-30T07:00:54Z Isfmiho 3 Typical HRTF/DRIR measurement setup figure added; old links remain as "source" wikitext text/x-wiki == General == [http://en.wikipedia.org/wiki/Head-related_transfer_function Head-related transfer functions (HRTFs)] describe the spatial filtering of the incoming sound due to the listener's anatomy. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are crucially important for the binaural reproduction of virtual acoustics. [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been measured by a number of laboratories and are typically stored in each lab's native file format. While the different formats are of advantage for each lab, an exchange of such data is difficult due to incompatibilities between formats. The '''spatially oriented format for acoustics (SOFA)''' aims at representing spatial data in a general way, allowing to store not only [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] but also more complex data, e.g., [http://en.wikipedia.org/wiki/Impulse_response directional room impulse responses] (DRIRs) measured with a multichannel microphone array excited by a loudspeaker array. In order to simplify the adaption of SOFA for various applications, examples of implementation of the format specifications are provided together with a collection of exemplary data sets converted to SOFA. == Typical measurement setups == One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were those of a [http://en.wikipedia.org/wiki/Dummy_head_recording dummy-head] microphone measured in an anechoic room [1]. Two microphones placed at the ear simulators were used for the recordings and one loudspeaker was used for the signal excitation. The loudspeaker was moved to the desired elevation and the mannequin was rotated to the desired azimuth. Taken together, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] for 710 spatial positions were measured at elevations from -40° to +90° in steps of 10° and 360° azimuthal range in steps of 5° and a constant distance of 1.4 m. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are provided as [http://en.wikipedia.org/wiki/Impulse_response impulse responses (IRs)] with the length of 512 samples at a sampling rate of 44.1 kHz. One of the first publicly available [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in human listeners was the CIPIC database [2]⁠. The measurements were performed at a constant distance of 1 m for 1250 spatial directions around the listener. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are available for 43 listeners as IRs of 200 samples at a sampling rate of 44.1 kHz. Since then many other [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIR databases have been made publicly available [3–8]⁠. [[File:Typical HRTF measurement.png|right|thumb|225px|Fig. 1: Typical HRTF/DRIR measurement setup]] All those measurement setups have the following properties in common. In an anechoic chamber or in a room, excitation signals are generated and microphones are used to record the incoming signals (see Fig. 1, [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download source]). The measurement is repeated while varying the spatial position of the excitation source relative to the listener, which is done by varying the position of the listener, the sound source, or both in different dimensions. Binaural [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement setups use only two microphones to record the left and right ear signals. However, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF]/DRIRs measurements may also consider multiple microphones, e.g., three microphones per head side in hearing-assist devices [7]⁠, tens of microphones arranged in an array structure at different directions and distances from the center [9]⁠, a multichannel microphone array arranged around the listeners in a reciprocal [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurement system [10], [11]⁠, multichannel microphone arrays for measuring DRIRs [12]⁠ or various microphone positions in a room, e.g., for concert-hall acoustics measurements [13]⁠. As a generalization, microphones and an object comprising those microphones can be identified. Thus, in this article, a microphone as the single receiver of the sound field is called the receiver, and the comprising all the receivers is called the listener, see Fig. 1 ([http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download source]). The sound source used for the excitation signal is not necessarily a single point source. Loudspeaker arrays were used, either to control the sound field surrounding the listener, e.g., wave-field synthesis [11], [14], [15]⁠, or higher-order Ambisonics [16], [17]⁠ or to control the radiation characteristics of the sound sources [18]⁠. Similarly to the concept of listener and receivers, in this article, the particular sources creating the excitation signal are called emitters and the object comprising the emitters is called source. Note that a measurement setup with a source with multiple emitters and a listener with multiple receivers has already been considered [19]⁠. In typical [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] measurements, only the direction of the incoming signal is varied. In more recent setups also different sound-ear distances have been considered [4], [11], [20]⁠. However, sometimes the variation of other parameters is of interest. For example, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] were measured as a function of the head orientation relative to the torso [21]⁠, or the room IRs were measured as a function of the room temperature [22]⁠. An [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] file format should thus consider even such parameters. == Aim of SOFA == While designing SOFA, we set up the following requirements: * Description of a measurement setup with arbitrary geometry, i.e., not limited to special cases like a regular grid, or a constant distance; * Self-describing data with a consistent definition, i.e., all the required information about the measurement setup must be provided as metadata in the file; * Flexibility to describe data of multiple conditions (listeners, distances, etc) in a single file; * Partial file and network support; * Available as binary file with data compression for efficient storage and transfer; * Predefined description conventions for the most common measurement setups. [[SOFA Specifications]] aim at fulfilling all those requirements. In a nutshell, the measurement setup is described by various objects and their relations. The information is stored in a numeric container based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. We consider a measurement as a discrete sampled observation done at a specific time and under a specific condition. Each measurement consists of data (e.g., an [http://en.wikipedia.org/wiki/Impulse_response impulse response, IR]) and is described by its corresponding dimensions and metadata. All measurements are stored in a single data structure (e.g., a matrix of IRs). A consistent description of measurement setups are given by [[SOFA conventions]]. == Other existing data formats == Beside SOFA, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] have been stored using different formats, all of them having advantages and disadvantages. The CIPIC database [2]⁠ provides a file per listener in either a plain text or Matlab (Mathworks, Inc.) file format. The directions are hard coded, i.e., the index of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] corresponds to a predefined direction used in the measurements. While the representation of [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from other directions is not allowed, anthropometric data have been stored within that format. The openDAFF package1, while similarly storing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] only in a regular angular distance, uses a key-value system for the description of the metadata which seems to be very promising. Other databases such as LISTEN [3]⁠ and ARI [6]⁠, consist of an [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF] matrix and additional matrices describing the direction of the corresponding [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTF], thus, allowing to represent [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from any direction. In that formats, [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] from each listener are stored in a separate file. In the database storing the [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] as a function of distance [4]⁠, the data are stored in a separate file for each distance. Combined with the necessity to store a separate file for each listener, those three latter formats would result in many files. The MARL-NYU database [23]⁠ harmonized the format of CIPIC, LISTEN, MIT, and others databases, and stores all those data in a single file. This concept seems to be promising when combined with a network interface and partial file access in the future. Most of those [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] are stored in Matlab formats, i.e., they use a Matlab file convention to store predefined matrices. In contrast, SDIF [24]⁠, a general format for storing audio-related data, has been adapted to [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] , allowing to store [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] of a single listener in a mixed text-based and binary representation. The concert-hall data [25]⁠, stored as compressed “.wav” files, are another example for a mixed-binary format, which further requires a description (separate text files) in order to being able to interpret the data. The [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs] measured in rooms (e.g., [8]⁠) are also Matlab files and the relationship between the data and the geometry of the measurement setup is provided in separate publications. ---- == References == [1] W. G. Gardner and K. D. Martin, “HRTF measurements of a KEMAR,” J Acoust Soc Am, vol. 97, pp. 3907–3908, 1995. [2] V. R. Algazi, R. O. Duda, D. M. Thompson, and C. Avendano, “The CIPIC HRTF database,” in IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, 2001, pp. 99–102. [3] O. Warusfel, “LISTEN HRTF database,” 2003. http://recherche.ircam.fr/equipes/salles/listen/. [4] H. Wierstorf, M. Geier, A. Raake, and S. Spors, “A free database of head-related impulse response measurements in the horizontal plane with multiple distances,” in 130th Convention of the Audio Engineering Society (aes), 2011, ebrief 6. [5] T. Nishino, S. Kajita, K. Takeda, and F. Itakura, “Interpolation of head related transfer functions of azimuth and elevation,” J Acoust Soc Jpn, vol. 57, pp. 685–692, 2001. [6] P. Majdak, M. J. Goupell, and B. Laback, “3-D localization of virtual sound sources: effects of visual environment, pointing method, and training.,” Atten Percept Psychophys, vol. 72, pp. 454–69, 2010. [7] H. Kayser, S.D.Ewert, J.Anemüller, T. Rohdenburg, V. Hohmann, and B. Kollmeier, “Database of multichannel in-ear and behind-the-ear head-related and binaural room impulse responses,” EURASIP J Advances Sig Proc, Article ID 298605, 10 pages, 2009. [8] M. Jeub, M. Schäfer, and P. Vary, “A binaural room impulse response database for the evaluation of dereverberation algorithms,” in 16th International Conference on Digital Signal Proc, 2009, pp. 1–5. [9] I. Balmages and B. Rafaely, “Open-sphere designs for spherical microphone arrays,” IEEE Trans Audio Speech Lang Proc, vol. 15, pp. 727–732, 2007. [10] D. N. Zotkin, R. Duraiswami, E. Grassi, and N. A. Gumerov, “Fast head-related transfer function measurement via reciprocity,” J Acoust Soc Am, vol. 120, pp. 2202–2215, 2006. [11] M. Pollow, M., Nguyen, K.-V., Warusfel, O., Carpentier, T., Müller-Trapet, M., Vorländer, M., and Noisternig, “Calculation of head-related transfer functions for arbitrary field points using spherical harmonics decomposition,” Acta Acust United Ac, vol. 89, pp. 72–82, 2012. [12] B. Khaykin, D., and Rafaely, “Acoustic analysis by spherical microphone array processing of room impulse responses,” J Acoust Soc Am, vol. 132, pp. 261–270, 2012. [13] T. Pätynen, J., Tervo, S., and Lokki, “Analysis of concert hall acoustics via visualizations of time-frequency and spatiotemporal responses,” J Acoust Soc Am, vol. 133, pp. 842–857, 2013. [14] A. J. Berkhout, “Holographic approach to acoustic sound control,” J Audio Eng Soc, vol. 36, pp. 977–995, 1988. [15] S. Ahrens, J., and Spors, “Wave field synthesis of a sound field described by spherical harmonics expansion coefficients,” J Acoust Soc Am, vol. 131, pp. 2190–2199, 2012. [16] M. A. Gerzon, “Ambisonics. Part two: Studio techniques,” Studio Sound, vol. 17, pp. 24–26, 1975. [17] M. Zotter, F., Pomberger, H., and Noisternig, “Energy-preserving ambisonic decoding,” Acta Acust United Ac, vol. 98, pp. 37–47, 2012. [18] B. Rafaely, “Spherical loudspeaker array for local active control of sound,” J Acoust Soc Am, vol. 125, pp. 3006–3017, 2009. [19] S. Clapp, A. Guthrie, J. Braasch, and N. Xiang, “The use of multi-channel microphone and loudspeaker arrays to evaluate room acoustics,” in Proceedings of the Acoustics, 2012, vol. 131, p. 3208. [20] S. Hosoe, K. I. Takanori Nishino, and K. Takeda, “Development of micro-dodecahedral loudspeaker for measuring head-related transfer functions in the proximal region,” in Proceedings of the IEEE Conference on Audio, Speech and Signal Processing (ICASSP), 2006, pp. 329–332. [21] M. Guldenschuh, A. Sontacchi, and F. Zotter, “HRTF modelling in due consideration variable torso reflections,” in Proceedings of the Acoustics’08, 2008, pp. 99–104. [22] G. W. Elko, E. Diethorn, and T. Gänsler, “Room impulse response variation due to thermal fluctuation and its impact on acoustic echo cancellation,” in International Workshop on Acoustic Echo and Noise Control (IWAENC2003), 2003. [23] A. Andreopoulou and A. Roginska, “Towards the creation of a standardized HRTF repository,” in 131th Convention of the Audio Engineering Society (AES), 2011, Convention Paper 8571. [24] D. Schwarz and M. Wright, “Extensions and applications of the SDIF sound description interchange format,” in Proceedings of the International Computer Music Conference, 2000. [25] J. Merimaa, T. Peltonen, and T. Lokki, “Concert hall impulse responses - Pori, Finland,” 2005. http://www.acoustics.hut.fi/projects/poririrs/. [26] H. Ziegelwanger and P. Majdak, “Continuous-direction model of the time-of-arrival in the head-related transfer functions,” J Acoust Soc Am, submitted. [27] M. Noisternig, F. Zotter, and B. F. Katz, “Reconstructing sound source directivity in virtual acoustic environments,” in Principles and Applications of Spatial Hearing, Y. Suzuki, D. S. Brungart, and H. Kato, Eds. Singapore: World Scientific Publishing, 2011, pp. 357–373. 5dd15e306af41c395e8f4d95c8fdfbcfbfeb6523 2 527 2245 2020-11-18T07:09:18Z Isfmiho 3 Creating user page for new user. wikitext text/x-wiki test user, can be accepted and deleted 6cf47598b0578f307955f3032e7f3700f3f71145 2247 2245 2020-11-18T07:11:07Z Isfmiho 3 Isfmiho moved page [[User:Testuser]] to [[User:Testente]]: Automatically moved page while merging the account "Testuser" to "[[User:Testente|Testente]]" wikitext text/x-wiki test user, can be accepted and deleted 6cf47598b0578f307955f3032e7f3700f3f71145 3 528 2246 2020-11-18T07:09:18Z Isfmiho 3 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 08:09, 18 November 2020 (CET) 668a7eb76f673c80be40c115d64f4b16b3f50337 2249 2246 2020-11-18T07:11:07Z Isfmiho 3 Isfmiho moved page [[User talk:Testuser]] to [[User talk:Testente]]: Automatically moved page while merging the account "Testuser" to "[[User:Testente|Testente]]" wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Isfmiho|Isfmiho]] ([[User talk:Isfmiho|talk]]) 08:09, 18 November 2020 (CET) 668a7eb76f673c80be40c115d64f4b16b3f50337 0 17 2251 2190 2020-11-27T07:58:19Z Isfmiho 3 /* General purpose database (HRTFs, PRTFs, and DRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' c03a5f6a8504482a6c371a1c58233ecd104bff06 2252 2251 2020-11-27T10:25:16Z Isfmiho 3 /* General purpose database (HRTFs, PRTFs, and DRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose [http://sofacoustics.org/data/database database] (HRTFs, PRTFs, and DRIRs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' bcf51749c750dcd27a17e6e8fb965620fd527980 0 531 2253 2020-12-02T11:59:16Z Isfmiho 3 Creating GeneralFIR-E wikitext text/x-wiki This conventions defines a general convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||1.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralFIRE||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIRE||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||metre||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double|| |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, metre||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |Data.IR||0||m||mREn||double||Impulse responses |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IRE, MRE||double||Additional delay of each IR (in samples) |} d89cc4930a1bb27bf0ebac0f59dd336ac53ad26a 2254 2253 2020-12-02T11:59:34Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed [[GeneralFIR]] convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||1.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralFIRE||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIRE||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||metre||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double|| |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, metre||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |Data.IR||0||m||mREn||double||Impulse responses |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 84f84e21debe19f050b41b7fcea1b63ae1273ceb 2255 2254 2020-12-02T12:00:04Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed [[GeneralFIR]] convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||1.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||GeneralFIRE||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIRE||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||metre||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double|| |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, metre||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |Data.IR||0||m||mREn||double||Impulse responses |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 6d77d9f362ea98b1d974b6aeae80b5198945120a 2265 2255 2020-12-02T12:49:47Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed [[GeneralFIR]] convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||GeneralFIR-E||rm|| ||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||2.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment||||m|| ||attribute|| |- |GLOBAL:DataType||FIR-E||rm|| ||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute||The room information can be arbitrary |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0 0]||m||I, R, M, RM, RCI, RCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double|| |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||I, E, M, EM, ECI, ECM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |Data.IR||0||m||mrne||double||Impulse responses |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 0e84b3325a20ac7fb822739661c5f95e69ae7cff 0 532 2256 2020-12-02T12:13:06Z Isfmiho 3 Creating SimpleFreeFieldHRSOS wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is TF. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||1.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldSOS||rm|| ||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:DataType||SOS||rm|| ||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0.09 0; 0 -0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |GLOBAL:DatabaseName||||m|| ||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m|| ||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |} 35c5feff05e746a3575e7ecd37e7d939f1156c5a 2257 2256 2020-12-02T12:14:09Z Isfmiho 3 summary fixed wikitext text/x-wiki This conventions defines free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is SOS. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||1.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldSOS||rm|| ||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:DataType||SOS||rm|| ||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0.09 0; 0 -0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |GLOBAL:DatabaseName||||m|| ||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m|| ||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |} 63719c016af6d9551118717349866537169eac99 2267 2257 2020-12-02T12:53:05Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is SOS. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||1.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldSOS||rm|| ||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:DataType||SOS||rm|| ||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0.09 0; 0 -0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |GLOBAL:DatabaseName||||m|| ||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m|| ||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |Data.SOS||permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} e3845c37c52f94ef0d831833bd73abd94f4d47b5 2281 2267 2021-01-11T10:44:00Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is SOS. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||1.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRSOS||rm|| ||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||2.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:DataType||SOS||rm|| ||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0.09 0; 0 -0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |GLOBAL:DatabaseName||||m|| ||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m|| ||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |Data.SOS||permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} f0dfaa749f2b832960d386ea373e144db0c85742 0 533 2258 2020-12-02T12:25:00Z Isfmiho 3 Creating GeneralTF-E wikitext text/x-wiki This conventions defines a general convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends [[GeneralTF]] by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- SOFA Vorbereitung |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF-E||rm|| ||attribute||This conventions stores TFs depending in the Emiiter for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralTF |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment||||m|| ||attribute|| |- |GLOBAL:DataType||TF-E||rm|| ||attribute||We store frequency-dependent data depending on the emitter here |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute||The room information can be arbitrary |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0 0]||m||I, R, M, RM, RCI, RCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||I, E, M, EM, ECI, ECM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |Data.Real||0||m||mrne||double||The real part of the complex spectrum |- |Data.Imag||0||m||MRNE||double||The imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||m||||attribute||Unit of the values given in N |- |Name||Default||Flags||Dimensions||Type||Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF-E||rm|| ||attribute||This conventions stores TFs depending in the Emiiter for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralTF |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |} 6095d259725648223ea896a8701fc1578d188085 2259 2258 2020-12-02T12:25:34Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends [[GeneralTF]] by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF-E||rm|| ||attribute||This conventions stores TFs depending in the Emiiter for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralTF |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment||||m|| ||attribute|| |- |GLOBAL:DataType||TF-E||rm|| ||attribute||We store frequency-dependent data depending on the emitter here |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute||The room information can be arbitrary |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0 0]||m||I, R, M, RM, RCI, RCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||I, E, M, EM, ECI, ECM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |Data.Real||0||m||mrne||double||The real part of the complex spectrum |- |Data.Imag||0||m||MRNE||double||The imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||m||||attribute||Unit of the values given in N |- |Name||Default||Flags||Dimensions||Type||Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF-E||rm|| ||attribute||This conventions stores TFs depending in the Emiiter for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralTF |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |} 11abd18dffe3cf8ef598995058697648ce0fbad9 2266 2259 2020-12-02T12:50:54Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends [[GeneralTF]] by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||GeneralTF-E||rm|| ||attribute||This conventions stores TFs depending in the Emiiter for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralTF |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment||||m|| ||attribute|| |- |GLOBAL:DataType||TF-E||rm|| ||attribute||We store frequency-dependent data depending on the emitter here |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute||The room information can be arbitrary |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0 0]||m||I, R, M, RM, RCI, RCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||I, E, M, EM, ECI, ECM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |Data.Real||0||m||mrne||double||The real part of the complex spectrum |- |Data.Imag||0||m||MRNE||double||The imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||m||||attribute||Unit of the values given in N |} b0009f7a7d56b9e90afbae00f2bc9a44cf507776 0 534 2260 2020-12-02T12:30:36Z Isfmiho 3 Creating General wikitext text/x-wiki This conventions defines a general convention with any datatype (no restrictions at all). The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||General||rm|| ||attribute||This conventions is for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:DataType||FIR||m|| ||attribute||The datatype can be arbitrary |- |GLOBAL:RoomType||free field||m|| ||attribute||The room information can be arbitrary |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:ListenerShortName||||||||attribute|| |- |GLOBAL:ListenerDescription||||||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ListenerView||[1 0 0]||||IC, MC||double|| |- |ListenerUp||[0 0 1]||||IC, MC||double|| |- |ListenerView:Type||cartesian||||||attribute|| |- |ListenerView:Units||metre||||||attribute|| |- |GLOBAL:ReceiverShortName||||||||attribute|| |- |GLOBAL:ReceiverDescription||||||||attribute|| |- |ReceiverPosition||[0 0 0]||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |ReceiverView||[1 0 0]||||RCI, RCM||double|| |- |ReceiverUp||[0 0 1]||||RCI, RCM||double|| |- |ReceiverView:Type||cartesian||||||attribute|| |- |ReceiverView:Units||metre||||||attribute|| |- |GLOBAL:SourceShortName||||||||attribute|| |- |GLOBAL:SourceDescription||||||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double|| |- |SourcePosition:Type||cartesian||m|| ||attribute|| |- |SourcePosition:Units||metre||m|| ||attribute|| |- |SourceView||[1 0 0]||||IC, MC||double|| |- |SourceUp||[0 0 1]||||IC, MC||double|| |- |SourceView:Type||cartesian||||||attribute|| |- |SourceView:Units||metre||||||attribute|| |- |GLOBAL:EmitterShortName||||||||attribute|| |- |GLOBAL:EmitterDescription||||||||attribute|| |- |EmitterPosition||[0 0 0]||m||IC, ECI, ECM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |EmitterView||[1 0 0]||||ECI, ECM||double|| |- |EmitterUp||[0 0 1]||||ECI, ECM||double|| |- |EmiiterView:Type||cartesian||||||attribute|| |- |EmitterView:Units||metre||||||attribute|| |- |Data.IR||0||m||mrn||double||Impulse responses |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IR, MR||double||Additional delay of each IR (in samples) |} 49389f93a07b34ccb3f03560e9fe1f63cd0ccfa4 0 535 2261 2020-12-02T12:33:00Z Isfmiho 3 Creating SimpleFreeFieldHRTF wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is TF. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRTF||rm|| ||attribute||This conventions is for HRTFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||2.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:DataType||TF||rm|| ||attribute|| |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0.09 0; 0 -0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |GLOBAL:DatabaseName||||m|| ||attribute||name of the database to which these data belong |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |Data.Real||[0 0]||m||mRn||double|| |- |Data.Imag||[0 0]||m||MRN||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} 8d9694a732227d48d468f6be952800cb3052d6e0 0 536 2262 2020-12-02T12:38:54Z Isfmiho 3 Creating SingleRoomSRIR wikitext text/x-wiki This conventions defines spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomSRIR||rm|| ||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:DataType||FIR||rm|| ||attribute||Shall be FIR |- |GLOBAL:RoomType||shoebox||m|| ||attribute||Shall be ‘shoebox’ or ‘dae’ |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:RoomDescription||||||||attribute||narrative description of the room |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:ListenerShortName||||||||attribute|| |- |GLOBAL:ListenerDescription||||||||attribute|| |- |ListenerPosition||[0 0 0] ||m||MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |GLOBAL:ReceiverShortName||||||||attribute|| |- |GLOBAL:ReceiverDescription||||||||attribute|| |- |ReceiverPosition||[0 0 0]||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||spherical||m|| ||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||degree, degree, metre||m|| ||attribute|| |- |ReceiverView||[1 0 0]||||RCI, RCM||double|| |- |ReceiverUp||[0 0 1]||||RCI, RCM||double|| |- |ReceiverView:Type||cartesian||||||attribute|| |- |ReceiverView:Units||metre||||||attribute|| |- |GLOBAL:SourceShortName||||||||attribute|| |- |GLOBAL:SourceDescription||||||||attribute|| |- |SourcePosition||[0 0 1]||m||MC||double|| |- |SourcePosition:Type||cartesian||m|| ||attribute|| |- |SourcePosition:Units||metre||m|| ||attribute|| |- |SourceView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |GLOBAL:EmitterShortName||||||||attribute|| |- |GLOBAL:EmitterDescription||||||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||spherical||m|| ||attribute|| |- |EmitterPosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterView||[1 0 0]||||ECI, ECM||double|| |- |EmitterUp||[0 0 1]||||ECI, ECM||double|| |- |EmiiterView:Type||cartesian||||||attribute||Shall be ‘cartesian’ or ‘spherical’, restricting to spatially discrete emitters. |- |EmitterView:Units||metre||||||attribute|| |- |Data.IR||0||m||mrn||double||Impulse responses |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IR, MR||double||Additional delay of each IR (in samples) |- |RoomCornerA||[0 0 0]||m||IC, MC||double|| |- |RoomCornerB||[1 2 3]||m||IC, MC||double|| |- |RoomCorners:Type||cartesian||m||||attribute|| |- |RoomCorners:Units||metre||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data. |} b25f4811432d38772cad9698622a9a45e3f88e62 2279 2262 2021-01-11T10:06:08Z Isfmiho 3 wikitext text/x-wiki This conventions defines spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomSRIR||rm|| ||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:DataType||FIR||rm|| ||attribute||Shall be FIR |- |GLOBAL:RoomType||shoebox||m|| ||attribute||Shall be ‘shoebox’ or ‘dae’ |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:RoomDescription||||||||attribute||narrative description of the room |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:ListenerShortName||||||||attribute|| |- |GLOBAL:ListenerDescription||||||||attribute|| |- |ListenerPosition||[0 0 0] ||m||MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |GLOBAL:ReceiverShortName||||||||attribute|| |- |GLOBAL:ReceiverDescription||||||||attribute|| |- |ReceiverPosition||[0 0 0]||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||spherical||m|| ||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||degree, degree, metre||m|| ||attribute|| |- |ReceiverView||[1 0 0]||||RCI, RCM||double|| |- |ReceiverUp||[0 0 1]||||RCI, RCM||double|| |- |ReceiverView:Type||cartesian||||||attribute|| |- |ReceiverView:Units||metre||||||attribute|| |- |GLOBAL:SourceShortName||||||||attribute|| |- |GLOBAL:SourceDescription||||||||attribute|| |- |SourcePosition||[0 0 1]||m||MC||double|| |- |SourcePosition:Type||cartesian||m|| ||attribute|| |- |SourcePosition:Units||metre||m|| ||attribute|| |- |SourceView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |GLOBAL:EmitterShortName||||||||attribute|| |- |GLOBAL:EmitterDescription||||||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||spherical||m|| ||attribute|| |- |EmitterPosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterView||[1 0 0]||||ECI, ECM||double|| |- |EmitterUp||[0 0 1]||||ECI, ECM||double|| |- |EmitterView:Type||cartesian||||||attribute||Shall be ‘cartesian’ or ‘spherical’, restricting to spatially discrete emitters. |- |EmitterView:Units||metre||||||attribute|| |- |Data.IR||0||m||mrn||double||Impulse responses |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IR, MR||double||Additional delay of each IR (in samples) |- |RoomCornerA||[0 0 0]||m||IC, MC||double|| |- |RoomCornerB||[1 2 3]||m||IC, MC||double|| |- |RoomCorners:Type||cartesian||m||||attribute|| |- |RoomCorners:Units||metre||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data. |} 2f479a4fd81aff3dd4ba9fe2da02c4d1f74a3e69 2282 2279 2021-01-11T12:29:18Z Isfmiho 3 wikitext text/x-wiki This conventions defines spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomSRIR||rm|| ||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:DataType||FIR||rm|| ||attribute||Shall be FIR |- |GLOBAL:RoomType||shoebox||m|| ||attribute||Shall be ‘shoebox’ or ‘dae’ |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:RoomDescription||||||||attribute||narrative description of the room |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:ListenerShortName||||||||attribute|| |- |GLOBAL:ListenerDescription||||||||attribute|| |- |ListenerPosition||[0 0 0] ||m||MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |GLOBAL:ReceiverShortName||||||||attribute|| |- |GLOBAL:ReceiverDescription||||||||attribute|| |- |ReceiverPosition||[0 0 0]||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||spherical||m|| ||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||degree, degree, metre||m|| ||attribute|| |- |ReceiverView||[1 0 0]||||RCI, RCM||double|| |- |ReceiverUp||[0 0 1]||||RCI, RCM||double|| |- |ReceiverView:Type||cartesian||||||attribute|| |- |ReceiverView:Units||metre||||||attribute|| |- |GLOBAL:SourceShortName||||||||attribute|| |- |GLOBAL:SourceDescription||||||||attribute|| |- |SourcePosition||[0 0 1]||m||MC||double|| |- |SourcePosition:Type||cartesian||m|| ||attribute|| |- |SourcePosition:Units||metre||m|| ||attribute|| |- |SourceView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |GLOBAL:EmitterShortName||||||||attribute|| |- |GLOBAL:EmitterDescription||||||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||spherical||m|| ||attribute|| |- |EmitterPosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterView||[1 0 0]||||ECI, ECM||double|| |- |EmitterUp||[0 0 1]||||ECI, ECM||double|| |- |EmitterView:Type||cartesian||||||attribute||Shall be ‘cartesian’ or ‘spherical’, restricting to spatially discrete emitters. |- |EmitterView:Units||metre||||||attribute|| |- |Data.IR||0||m||mrn||double||Impulse responses |- |Data.SamplingRate||48000||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IR, MR||double||Additional delay of each IR (in samples) |- |RoomCornerA||[0 0 0]||||IC, MC||double|| |- |RoomCornerB||[1 2 3]||||IC, MC||double|| |- |RoomCorners:Type||cartesian||||||attribute|| |- |RoomCorners:Units||metre||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data. |} 44762096c0aa8cc39b706529cb557041eab4154e 0 5 2263 2238 2020-12-02T12:41:22Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[SHFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRTF, the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! f3c89947c10608b2c96dea78bc2316fcef091dca 2271 2263 2020-12-02T13:55:39Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * '''Flags''': ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 4bebe611335c328b304ea08a62d732ab607f6a23 2288 2271 2021-01-14T10:38:31Z Isfmiho 3 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * '''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! a6720c362fad137bdaff0c56fefea51b9c2c1bb5 2289 2288 2021-01-14T10:41:47Z Isfmiho 3 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! aee27af556eed6c33e23de361fd19296087be032 2292 2289 2021-01-14T13:06:45Z Isfmiho 3 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata (see [[SOFA specifications]] for more explanations) ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) :: {| class="wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension |style="color:gray" |constant, always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet |style="color:gray" |constant, always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! c0e72dd45c35cfa551d0353794db6fa05c113d8f 2293 2292 2021-01-14T14:32:20Z Isfmiho 3 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[SimpleFreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. SimpleFreeFieldDirectivityTF is the standardized version of the previously proposed FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 2a722767a66c21a6ee28481e9fc4b2eaa6114653 0 537 2264 2020-12-02T12:43:23Z Isfmiho 3 Creating SingleRoomMIMOSRIR wikitext text/x-wiki This conventions defines SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomMIMOSRIR||rm|| ||attribute||Single-room multiple-input multiple-output spatial room impulse responses, depending on Emitters |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:DataType||FIR-E||rm|| ||attribute||Shall be FIR-E |- |GLOBAL:RoomType||shoebox||m|| ||attribute||Shall be ‘shoebox’ or ‘dae’ |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:RoomDescription||||||||attribute||narrative description of the room |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:ListenerShortName||||||||attribute|| |- |GLOBAL:ListenerDescription||||||||attribute|| |- |ListenerPosition||[0 0 0] ||m||MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |GLOBAL:ReceiverShortName||||||||attribute|| |- |GLOBAL:ReceiverDescription||||||||attribute|| |- |ReceiverPosition||[0 0 0]||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||spherical||m|| ||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||degree, degree, metre||m|| ||attribute|| |- |ReceiverView||[1 0 0]||||RCI, RCM||double|| |- |ReceiverUp||[0 0 1]||||RCI, RCM||double|| |- |ReceiverView:Type||cartesian||||||attribute|| |- |ReceiverView:Units||metre||||||attribute|| |- |GLOBAL:SourceShortName||||||||attribute|| |- |GLOBAL:SourceDescription||||||||attribute|| |- |SourcePosition||[0 0 1]||m||MC||double|| |- |SourcePosition:Type||cartesian||m|| ||attribute|| |- |SourcePosition:Units||metre||m|| ||attribute|| |- |SourceView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |GLOBAL:EmitterShortName||||||||attribute|| |- |GLOBAL:EmitterDescription||||||||attribute|| |- |EmitterPosition||[0 0 0]||m||IC, ECI, ECM||double||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |EmitterPosition:Type||spherical||m|| ||attribute|| |- |EmitterPosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterView||[1 0 0]||||ECI, ECM||double|| |- |EmitterUp||[0 0 1]||||ECI, ECM||double|| |- |EmiiterView:Type||cartesian||||||attribute|| |- |EmitterView:Units||metre||||||attribute|| |- |Data.IR||0||m||mrne||double||Impulse responses |- |Data.SamplingRate||48000||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||hertz||m||||attribute||Unit of the sampling rate |- |Data.Delay||0||m||IRI, MRI, MRE||double||Additional delay of each IR (in samples) |- |RoomCornerA||[0 0 0]||m||IC, MC||double|| |- |RoomCornerB||[1 2 3]||m||IC, MC||double|| |- |RoomCorners:Type||cartesian||m||||attribute|| |- |RoomCorners:Units||metre||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data. |} 393db8946e90c3f20802c303769e0f57a9004c07 0 498 2268 2214 2020-12-02T12:56:46Z Isfmiho 3 version 1.0 added wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||2.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||FreeFieldDirectivityTF||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||cartesian||m||||attribute|| |- |ListenerUp:Units||metre||m||||attribute|| |- |ReceiverPosition||[0 0 1]||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||spherical||m||||attribute|| |- |ReceiverPosition:Units||degree, degree, metre||m||||attribute|| |- |SourcePosition||[0 0 0] ||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||metre||m||||attribute|| |- |SourcePosition:Reference||||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||[1 0 0]||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |SourceView:Reference||||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||[0 0 1]||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||cartesian||m||||attribute|| |- |SourceUp:Units||metre||m||||attribute|| |- |SourceUp:Reference||||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||[0 0 0]||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |EmitterDescription||||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||0||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||0||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||0||m||MRN||double||Imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N:LongName||frequency||m||||attribute|| |- |N:Units||Hertz||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 2317ba21989109188a118e12b2682facae3aca41 2269 2268 2020-12-02T13:09:47Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||2.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||FreeFieldDirectivityTF||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||cartesian||m||||attribute|| |- |ListenerUp:Units||metre||m||||attribute|| |- |ReceiverPosition||[0 0 1]||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||spherical||m||||attribute|| |- |ReceiverPosition:Units||degree, degree, metre||m||||attribute|| |- |SourcePosition||[0 0 0] ||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||metre||m||||attribute|| |- |SourcePosition:Reference||||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||[1 0 0]||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |SourceView:Reference||||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||[0 0 1]||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||cartesian||m||||attribute|| |- |SourceUp:Units||metre||m||||attribute|| |- |SourceUp:Reference||||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||[0 0 0]||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |EmitterDescription||||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||0||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||0||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||0||m||MRN||double||Imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N:LongName||frequency||m||||attribute|| |- |N:Units||Hertz||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 8ef4cdf47e2ff89a346835421b2e237a2a905152 2280 2269 2021-01-11T10:12:27Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||2.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldDirectivityTF||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||cartesian||m||||attribute|| |- |ListenerUp:Units||metre||m||||attribute|| |- |ReceiverPosition||[0 0 1]||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||spherical||m||||attribute|| |- |ReceiverPosition:Units||degree, degree, metre||m||||attribute|| |- |SourcePosition||[0 0 0] ||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||metre||m||||attribute|| |- |SourcePosition:Reference||||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||[1 0 0]||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |SourceView:Reference||||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||[0 0 1]||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||cartesian||m||||attribute|| |- |SourceUp:Units||metre||m||||attribute|| |- |SourceUp:Reference||||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||[0 0 0]||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |EmitterDescription||||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||0||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||0||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||0||m||MRN||double||Imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N:LongName||frequency||m||||attribute|| |- |N:Units||Hertz||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} b7f1645fb2b690ff3a6345e7fffa1c0b5323c0d3 2283 2280 2021-01-11T12:30:29Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||2.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldDirectivityTF||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||cartesian||m||||attribute|| |- |ListenerUp:Units||metre||m||||attribute|| |- |ReceiverPosition||[0 0 1]||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||spherical||m||||attribute|| |- |ReceiverPosition:Units||degree, degree, metre||m||||attribute|| |- |SourcePosition||[0 0 0] ||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||metre||m||||attribute|| |- |SourcePosition:Reference||||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||[1 0 0]||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |SourceView:Reference||||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||[0 0 1]||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||cartesian||m||||attribute|| |- |SourceUp:Units||metre||m||||attribute|| |- |SourceUp:Reference||||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||[0 0 0]||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |EmitterDescription||||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||0||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||0||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||0||m||MRN||double||Imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N:LongName||frequency||m||||attribute|| |- |N:Units||Hertz||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} b1a6bbc76ecc9c9c122382ac540a709c11704254 2284 2283 2021-01-11T12:59:11Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||2.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldDirectivityTF||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||cartesian||||||attribute|| |- |ListenerUp:Units||metre||||||attribute|| |- |ReceiverPosition||[0 0 1]||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||spherical||m||||attribute|| |- |ReceiverPosition:Units||degree, degree, metre||m||||attribute|| |- |SourcePosition||[0 0 0] ||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||metre||m||||attribute|| |- |SourcePosition:Reference||||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||[1 0 0]||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |SourceView:Reference||||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||[0 0 1]||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||cartesian||m||||attribute|| |- |SourceUp:Units||metre||m||||attribute|| |- |SourceUp:Reference||||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||[0 0 0]||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |EmitterDescription||||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||0||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||0||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||0||m||MRN||double||Imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N:LongName||frequency||m||||attribute|| |- |N:Units||Hertz||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 60be3c5ff122b64e090232fc1bff7c4f0166e630 0 459 2270 2173 2020-12-02T13:14:41Z Isfmiho 3 version 1.0 added wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.2.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm|| ||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment||||m|| ||attribute|| |- |GLOBAL:DataType||FIR||rm|| ||attribute||We will store IRs here |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute||Room type is not relevant here |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0.09 0; 0 -0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0.09 0; 0 -0.09 0]||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m|| ||attribute|| |- |EmitterPosition:Units||metre||m|| ||attribute|| |- |Data.IR||[0 0]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |- |GLOBAL:DatabaseName||||m|| ||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||||m|| ||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||{''}||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||{''}||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||{''}||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||{''}||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||0||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Version 0.2 === This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} === Version 0.1, previously proposed as HeadphoneIR (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} 3c83149d4b297335cc88f40de5e5ae0092c3f1c2 0 538 2272 2020-12-02T14:02:58Z Isfmiho 3 Creating FreeFieldHRTF wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm|| ||attribute|| |- |GLOBAL:Version||2.0||rm|| ||attribute|| |- |GLOBAL:SOFAConventions||FreeFieldHRTF||rm|| ||attribute||This conventions is for HRTFs created under conditions where room information is irrelevant and stored as SH coefficients |- |GLOBAL:SOFAConventionsVersion||1.0||rm|| ||attribute|| |- |GLOBAL:APIName||||rm|| ||attribute|| |- |GLOBAL:APIVersion||||rm|| ||attribute|| |- |GLOBAL:ApplicationName|||||| ||attribute|| |- |GLOBAL:ApplicationVersion|||||| ||attribute|| |- |GLOBAL:AuthorContact||||m|| ||attribute|| |- |GLOBAL:Comment|||||| ||attribute|| |- |GLOBAL:DataType||TF-E||rm|| ||attribute|| |- |GLOBAL:History|||||| ||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m|| ||attribute|| |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||||m|| ||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m|| ||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m|| ||attribute|| |- |GLOBAL:DateModified||||m|| ||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m|| ||attribute|| |- |ListenerPosition:Units||metre||m|| ||attribute|| |- |ReceiverPosition||[0 0.09 0; 0 -0.09 0]||m||RCI, RCM||double|| |- |ReceiverPosition:Type||cartesian||m|| ||attribute|| |- |ReceiverPosition:Units||metre||m|| ||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Source position is assumed to be the ListenerPosition in order to reflect Emitters surrounding the Listener |- |SourcePosition:Type||spherical||m|| ||attribute|| |- |SourcePosition:Units||degree, degree, metre||m|| ||attribute|| |- |EmitterPosition||[0 0 0]||m||IC, ECI, ECM||double||Emitter positions are irrelevant because they data is spatially continuous |- |EmitterPosition:Type||harmonics||m|| ||attribute||Spatially continuous representation by means of harmonics |- |EmitterPosition:Units||spherical||m|| ||attribute||3D representation |- |GLOBAL:DatabaseName||||m|| ||attribute||Name of the database to which these data belong |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |Data.Real||[0 0]||m||mrne||double|| |- |Data.Imag||[0 0]||m||MRNE||double|| |- |N||0||m||N||double|| |- |N_LongName||frequency||||||attribute|| |- |N_Units||hertz||||||attribute|| |} d75a92bfa086067aa3f272cfdcf1908382e04cdd 0 17 2273 2252 2020-12-04T10:09:07Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln): ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' d9ad21eb2da7e9e9ac0dc25c5a7e99e2eb8bc71e 2274 2273 2020-12-10T07:48:38Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [http://www.kfs.oeaw.ac.at/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' db126f78e8d53aaa46f279ff165feef2a215561c 2285 2274 2021-01-11T13:28:30Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: http://www.kfs.oeaw.ac.at/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 1c526eeb91bd0142423cc9a58739368631bf7dfb 2286 2285 2021-01-11T13:29:22Z Isfmiho 3 /* Other repositories */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/amt amt]: HRTFs for the various models from the [http://amtoolbox.sourceforge.net AMToolbox] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 4cc580bdd1c5c3b4bc9ca9e789d0b3adf289d909 2301 2286 2021-01-15T10:08:26Z Isfmiho 3 /* Special purpose */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) ''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 54db1de899ee9169655324b39b1c1ecfec4287b5 2302 2301 2021-01-15T12:20:55Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa)''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 68fc47cb0963c56e862d5519e04eaefa329801e7 0 11 2275 2237 2021-01-08T13:01:11Z Isfmiho 3 /* Specifications */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 2.0) === This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 2.0) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ad6c58af184c63d5547dfd2add7bd774ada12a38 2276 2275 2021-01-08T13:01:42Z Isfmiho 3 /* SOS (SOFA 2.0) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 2.0) === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 2.0) === FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 10a7932b6862494a97699df5690002189b4bbe07 2277 2276 2021-01-08T13:01:54Z Isfmiho 3 /* FIR-E (SOFA 2.0) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 2.0) === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 2.0) === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} f0f50e14e2ec3961acd2e413f0dc5d6cb0c1e0ca 2278 2277 2021-01-08T13:05:28Z Isfmiho 3 /* Specifications */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === FIR (SOFA 1.0) === For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} === TF (SOFA 1.0) === Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} === SOS (SOFA 2.0) === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} === FIR-E (SOFA 2.0) === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === FIRE (SOFA 1.0, deprecated) === FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} fe4b3321672e3de621f7c962152220fd31766419 2294 2278 2021-01-15T08:05:44Z Isfmiho 3 /* Data Types */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.0 === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use FIR-E instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.0 === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} 0af4b3124ded61a9092432efea42ec9fd695916c 2295 2294 2021-01-15T08:07:54Z Isfmiho 3 /* FIRE (deprecated) */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.0 === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.0 === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} e87cca859f77a50dad72cfffc90a4fa4eee6de39 2296 2295 2021-01-15T08:11:15Z Isfmiho 3 /* SOFA 2.0 */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.0 === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.0 === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). 5ce6654e5d53bbec0fac67a9aed653cd34902730 2297 2296 2021-01-15T08:15:59Z Isfmiho 3 /* TF-E */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.0 === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.0 === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} 8e5a95f57d862a897600ed1341d6ec42c5e2bb5d 2298 2297 2021-01-15T08:16:49Z Isfmiho 3 /* FIR-E */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.0 === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.0 === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} fdfd05318e2ed26b563f58299bc5cbaa0284ff92 2299 2298 2021-01-15T08:16:58Z Isfmiho 3 /* TF */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.0 === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.0 === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} 1b84ea006784524c2ec91b8cdaec7ae1c5e32048 2300 2299 2021-01-15T08:19:30Z Isfmiho 3 /* Data Types */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.0 === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.0 === Remark: SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} cc990089e7911d86c5df280984e7969cd2c180cf 0 476 2287 1990 2021-01-14T09:51:52Z Isfmiho 3 /* Description */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is [http://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#SOS_.28proposed.29 SOS], not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). It is recommended to use [[SimpleFreeFieldHRSOS]] instead, which is defined in AES69-2020 (SOFA 2.0). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note: * In contrast to SimpleFreeFieldHRIR 1.0, SimpleFreeFieldSOS 1.0 has not been included in the standard. But it can be considered as stable. * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} ec22ecadd2d56c78f462804265df8fd7a7801dfb 0 286 2290 1964 2021-01-14T10:45:04Z Isfmiho 3 wikitext text/x-wiki This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |} 9dc8c44ef65ebd605abe25bfbefabf3faa1467ac 2291 2290 2021-01-14T10:46:15Z Isfmiho 3 wikitext text/x-wiki This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>General</nowiki>||rm||||attribute||This conventions is for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||m||||attribute||The datatype can be arbitrary |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmiiterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |} 7a5fb9ae38f3e2c9f7bbc4f5a3e3889878c5a20a 0 498 2303 2284 2021-01-20T10:38:24Z Isfmiho 3 Isfmiho moved page [[SimpleFreeFieldDirectivityTF]] to [[FreeFieldDirectivityTF]] over redirect: FreeFieldDirectivityTF is not going to be "simple" anymore; now it is also according to standard wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||2.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldDirectivityTF||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||cartesian||||||attribute|| |- |ListenerUp:Units||metre||||||attribute|| |- |ReceiverPosition||[0 0 1]||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||spherical||m||||attribute|| |- |ReceiverPosition:Units||degree, degree, metre||m||||attribute|| |- |SourcePosition||[0 0 0] ||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||metre||m||||attribute|| |- |SourcePosition:Reference||||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||[1 0 0]||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |SourceView:Reference||||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||[0 0 1]||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||cartesian||m||||attribute|| |- |SourceUp:Units||metre||m||||attribute|| |- |SourceUp:Reference||||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||[0 0 0]||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |EmitterDescription||||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||0||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||0||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||0||m||MRN||double||Imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N:LongName||frequency||m||||attribute|| |- |N:Units||Hertz||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 60be3c5ff122b64e090232fc1bff7c4f0166e630 2307 2303 2021-01-20T10:39:37Z Isfmiho 3 /* Version 0.2 */ wikitext text/x-wiki == Description == SimpleFreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||2.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldDirectivityTF||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||cartesian||||||attribute|| |- |ListenerUp:Units||metre||||||attribute|| |- |ReceiverPosition||[0 0 1]||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||spherical||m||||attribute|| |- |ReceiverPosition:Units||degree, degree, metre||m||||attribute|| |- |SourcePosition||[0 0 0] ||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||metre||m||||attribute|| |- |SourcePosition:Reference||||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||[1 0 0]||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |SourceView:Reference||||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||[0 0 1]||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||cartesian||m||||attribute|| |- |SourceUp:Units||metre||m||||attribute|| |- |SourceUp:Reference||||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||[0 0 0]||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |EmitterDescription||||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||0||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||0||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||0||m||MRN||double||Imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N:LongName||frequency||m||||attribute|| |- |N:Units||Hertz||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} f4ad72fde707141dcb247e28b38a2b930797bb63 2308 2307 2021-01-20T10:39:55Z Isfmiho 3 /* Description */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||2.0||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldDirectivityTF||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||1.0||rm||||attribute|| |- |GLOBAL:DataType||TF||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||free field||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||||m||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||[0 0 0] ||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||metre||m||||attribute|| |- |ListenerView||[1 0 0]||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||metre||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||cartesian||||||attribute|| |- |ListenerUp:Units||metre||||||attribute|| |- |ReceiverPosition||[0 0 1]||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||spherical||m||||attribute|| |- |ReceiverPosition:Units||degree, degree, metre||m||||attribute|| |- |SourcePosition||[0 0 0] ||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||metre||m||||attribute|| |- |SourcePosition:Reference||||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||[1 0 0]||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||cartesian||m||||attribute|| |- |SourceView:Units||metre||m||||attribute|| |- |SourceView:Reference||||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||[0 0 1]||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||cartesian||m||||attribute|| |- |SourceUp:Units||metre||m||||attribute|| |- |SourceUp:Reference||||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||[0 0 0]||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||metre||m||||attribute|| |- |EmitterDescription||||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||0||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||0||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||0||m||MRN||double||Imaginary part of the complex spectrum |- |N||0||m||N||double||Frequency values |- |N:LongName||frequency||m||||attribute|| |- |N:Units||Hertz||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 9fd8ab01726ef180a6f8cd2650c636225607ad2b 2311 2308 2021-01-20T10:44:49Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerUp:Units||<nowiki>metre</nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki></nowiki>||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} c7553b061ece3bac902d37b6f852d82a70b333e4 2312 2311 2021-01-20T10:46:16Z Isfmiho 3 /* Version 0.2 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerUp:Units||<nowiki>metre</nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RCI, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki></nowiki>||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||MS||attribute||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded and will be called "FreeFieldDirectivityTF" from version 1.0 again (according to SOFA standard). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 772ae5e5ca011eff24a168ac4ad5cc147edef141 2315 2312 2021-02-12T09:47:45Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki></nowiki>||||IC, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||MS||attribute||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded and will be called "FreeFieldDirectivityTF" from version 1.0 again (according to SOFA standard). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} adc3615f572dd548a28e03dee3f0515bbe00aae5 0 539 2304 2021-01-20T10:38:24Z Isfmiho 3 Isfmiho moved page [[SimpleFreeFieldDirectivityTF]] to [[FreeFieldDirectivityTF]] over redirect: FreeFieldDirectivityTF is not going to be "simple" anymore; now it is also according to standard wikitext text/x-wiki #REDIRECT [[FreeFieldDirectivityTF]] d174947936036f09b4083d53183a0ec505977cc9 1 499 2305 2216 2021-01-20T10:38:25Z Isfmiho 3 Isfmiho moved page [[Talk:SimpleFreeFieldDirectivityTF]] to [[Talk:FreeFieldDirectivityTF]] over redirect: FreeFieldDirectivityTF is not going to be "simple" anymore; now it is also according to standard wikitext text/x-wiki changes: * TuningFrequency:LongName: not required, because TuningFrequency is always frequency. * TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always. * ListenerView/Up: added because required to define the orientation of the microphone array * SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same. * EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore. * EmitterDescription: renamed to MIDINoteDescription because it describes a note. * GLOBAL:MusicianPosition: renamed to GLOBAL:Musician To be discussed: * MIDINote (and MIDINoteDescription) '''or''' Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex... * Conventions name: if we want to keep it simple, we could ignore the room (the usual case when talking about directivity). Then, the convention could be called FreeFieldDirectivityX, with X={TF|FIR}. Note that I skipped the "MusicalInstrument" because this is limiting and we consider directivity of loudspeakers and singers already now, i.e., more than just instruments. efbc51563e204ad6720c0aeddfca0bf9b1d6d39f 1 540 2306 2021-01-20T10:38:25Z Isfmiho 3 Isfmiho moved page [[Talk:SimpleFreeFieldDirectivityTF]] to [[Talk:FreeFieldDirectivityTF]] over redirect: FreeFieldDirectivityTF is not going to be "simple" anymore; now it is also according to standard wikitext text/x-wiki #REDIRECT [[Talk:FreeFieldDirectivityTF]] 93e22581536cff7d7d174274526161fe8d6bdaa8 0 5 2309 2293 2021-01-20T10:40:43Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[FreeFieldDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[MusicalInstrumentDirectivityTF]]: use [[SimpleFreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! a523c62b9f12159a00da37dd626cb1c70ce7d2c6 2310 2309 2021-01-20T10:41:22Z Isfmiho 3 /* Deprecated SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 93d4ee3315ae3f6da8d86b58de0778fc6741808a 0 17 2313 2302 2021-02-02T13:20:12Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa)''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. '''New: Directivity Data:''' * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ Directivity Data]''': One data sets of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet (recorded with a 32 channel microphone array) from the TU Berlin. ''(Credit: David Ackermann, Germany)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 1bb868fab3763d9c1784f721e7dc9a855101685a 2314 2313 2021-02-02T13:20:46Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa)''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. '''New: Directivity Data:''' * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ Directivity Data]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' c97a79947592f0cd2835b6f70068bd4368ee231d 2316 2314 2021-02-12T12:12:46Z Isfmiho 3 /* Special purpose */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa)''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. '''New: Directivity Data:''' * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ Directivity Data]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: Test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 5bc9fa27e8553c37346293ff8242b92cdc5c612a 2317 2316 2021-02-12T12:14:02Z Isfmiho 3 /* Special purpose */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa)''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. '''New: Directivity Data:''' * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ Directivity Data]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Special purpose == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' f161894c1202200045fee9d0195cea3b6e96b639 2318 2317 2021-02-12T12:14:23Z Isfmiho 3 /* Special purpose */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa)''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. '''New: Directivity Data:''' * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ Directivity Data]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)''. == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' d136b1fc9cfa40331ebae02947e680638bcc2b83 2319 2318 2021-02-15T09:27:03Z Petibub 4 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * '''New: [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa)''' with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)''. '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 2a52daf2027160df284d57046edb97493a6cc9e7 2320 2319 2021-02-15T09:34:30Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. '''New: PRTFs: ''' * '''[http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings)''': 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)''. '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 3a4d9788ff88f0d7cf2fd99de2036703210f8975 2322 2320 2021-02-15T09:37:36Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * '''New: [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) ''' from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)''. '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' d978b33986098ced2ed51e7901b9afc526bd6032 2324 2322 2021-02-15T09:38:14Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)''. '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' dc3d61ab3697f57e105ce1851e16dfa35768f261 2327 2324 2021-02-15T09:43:42Z Isfmiho 3 /* Directivities (sources and receivers) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''[http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 1a54f6cb49501b37bd65da840891491bd666fa98 2329 2327 2021-02-15T09:44:52Z Isfmiho 3 /* Directivities (sources and receivers) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/sofa_api_mo_test Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 83a541ab695b674eeedb3c405ee87a25e3185905 2330 2329 2021-02-15T10:30:06Z Isfmiho 3 /* SOFA Test Files */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/test/ Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files named according to their conventions * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' ece3e20aceafc1efbca77faadbd9a4987bedf56b 2331 2330 2021-03-04T09:18:46Z Isfmiho 3 /* SOFA Test Files */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/test/ Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 6727e2fb407fbeb75665d20746347781b20ea1a1 2332 2331 2021-03-04T13:00:07Z Isfmiho 3 /* SOFA Test Files */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == SOFA Test Files == * [http://sofacoustics.org/data/examples/ Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 71bea8045151e3b3d50b5442897f2adabc289ec2 2333 2332 2021-03-04T13:00:28Z Isfmiho 3 /* SOFA Test Files */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Test & Example SOFA Files == * [http://sofacoustics.org/data/examples/ Test files]: SOFA test files for stable [[SOFA_conventions|conventions]], files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 9bdb8c24c1a189b636bd7dc32eb6fc2a65146121 2334 2333 2021-03-11T06:47:17Z Isfmiho 3 /* Example & Test SOFA Files */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [http://www.audiogroup.web.fh-koeln.de/ku100hrir.html Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[http://audiogroup.web.th-koeln.de/ku100nfhrir.html Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of Neumann KU100] (KU100*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. **[http://audiogroup.web.th-koeln.de/headgear.html Head-gear HRTFs of HEAD acoustics HMS II] (HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' bd749a7d7dd9fc8a9a35da9dcd963ad86041e4d5 2343 2334 2021-06-25T08:06:48Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa)): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' b6c38239d9938aa2e98009c2d62ba41033987c23 2344 2343 2021-06-25T08:07:09Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [http://audiogroup.web.th-koeln.de/wdr_irc.html here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' f24c9ac6f726025b27f2b773bba57e4123967f60 2345 2344 2021-06-25T08:08:12Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs]''' from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * '''New: [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR]''' dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' edfd572d86ec2a4fb36f221898d26b84b5cd9aea 2347 2345 2021-06-28T08:35:12Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * '''New: [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]''': One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 4cb92be43a761689fe2a3e1f5b265e21cce4a325 2348 2347 2021-06-28T09:02:44Z Isfmiho 3 /* Directivities (sources and receivers) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' 1ffb1cde21563778865e337c27652e7c71cff212 2350 2348 2021-06-28T09:13:18Z Isfmiho 3 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 8393bdfcad8a2d7df1ad0ffe3d129cd918626d6c 0 1 2321 2239 2021-02-15T09:34:34Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. ''' New: CHEDAR: Numerically calculated HRTFs (with 3D meshes provided)!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: 3D Tune-In Toolkit and Anaglyph added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 15.01.2021: Aachen: High-resolution HRTFs added (Credit: Janina Fels, Aachen) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France). * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released e52bf36b61d36189bdab41592ad266fa4603e292 2323 2321 2021-02-15T09:37:42Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. ''' New: CHEDAR: Numerically calculated HRTFs (with 3D meshes provided)!''' * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). ''' New: 3D Tune-In Toolkit and Anaglyph added!''' * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France). * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released acaf1c9d81c4ecfc5362ba7fcdea532c5ec0d986 2325 2323 2021-02-15T09:40:45Z Isfmiho 3 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 3d65f8cdf2e1f25080986ad17af7255d810427d5 2326 2325 2021-02-15T09:41:01Z Isfmiho 3 wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 407ec93594954e37bee31e905a318950c44dc1e5 2328 2326 2021-02-15T09:44:00Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released cb733410c71770b01cb9fbf00befb19e341207d5 2 541 2335 2021-05-31T09:08:18Z Jw 959 Creating user page for new user. wikitext text/x-wiki Just testing if I (jw) will get a notice of a user request, having created an account jw with administration rights. You (miho and piotr) can ignore this request - I'll deal with it. d570e315805ed73035003ef5aeeaee492c63871d 3 542 2336 2021-05-31T09:08:18Z Jw 959 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Jw|Jw]] ([[User talk:Jw|talk]]) 11:08, 31 May 2021 (CEST) cb1e8c8e4619fdbbe3b721149f50fd9867b0e9ed 2 543 2337 2021-06-02T09:17:10Z Petibub 4 Creating user page for new user. wikitext text/x-wiki Binaural audio enthusiast working on some projects: https://kutt.it/Binaural - Binaural audio intro https://kutt.it/BinauralDatabase - Binaural database (configurations, demos, ratings, guides, etc.) https://kutt.it/BinauralDatabaseSearch - Binaural database search engine https://kutt.it/BinauralDatabaseCatalog - Binaural database guide showcase https://kutt.it/BinauralDatabaseAdd - Report and review binaural audio in games/programs/websites/music/movies/etc. https://kutt.it/BinauralSoftware - Binaural audio software https://kutt.it/BinauralHRTF - Binaural profile (HRTF) sample database for comparison https://kutt.it/BinauralResources - Misc. resources https://kutt.it/BinauralExperiments - Binaural audio experiments e85ca8fce109aab11af06c99ae2c04551978670d 3 544 2338 2021-06-02T09:17:10Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 11:17, 2 June 2021 (CEST) 58553905550f49aebba89f898a5221c7ba2ddcb4 2 545 2339 2021-06-16T07:21:27Z Petibub 4 Creating user page for new user. wikitext text/x-wiki T.S. Qu got B.Eng. and M.Eng degree from Jilin University of Technology in 1993 and 1999. In 2002, he got Ph.D. degree from Jilin University. Then, he became a post-doctor of Peking University. In 2004, he finished the post-doctor work and became an assistant professor in Peking University. And now, he is an associate professor in Peking University. From 2011.3 to 2012.3, he went to Michigan State University as a visiting scholar. His principal interests are in acoustic signal processing, binaural auditory model and virtual sound. 7b0bf3c72035b1ee387e10eb166a59edd60ec36c 3 546 2340 2021-06-16T07:21:27Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 09:21, 16 June 2021 (CEST) 56d1552a47835288d507abdb697877de724e0dfe 2 547 2341 2021-06-16T07:21:56Z Petibub 4 Creating user page for new user. wikitext text/x-wiki T.S. Qu got B.Eng. and M.Eng degree from Jilin University of Technology in 1993 and 1999. In 2002, he got Ph.D. degree from Jilin University. Then, he became a post-doctor of Peking University. In 2004, he finished the post-doctor work and became an assistant professor in Peking University. And now, he is an associate professor in Peking University. From 2011.3 to 2012.3, he went to Michigan State University as a visiting scholar. His principal interests are in acoustic signal processing, binaural auditory model and virtual sound. 7b0bf3c72035b1ee387e10eb166a59edd60ec36c 3 548 2342 2021-06-16T07:21:56Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 09:21, 16 June 2021 (CEST) 56d1552a47835288d507abdb697877de724e0dfe 1 463 2346 2242 2021-06-26T21:39:43Z 3DJ 961 /* Binaural Audio database */ new section wikitext text/x-wiki == 3D3A LAB Database == Hello! Is there a specific reason the 3D3A LAB Database is not present in the SOFA repository? here is a link to the dataset: https://www.princeton.edu/3D3A/HRTFMeasurements.html I hope I'm using this tool correctly. Best, == Binaural Audio database == Greetings, I just wanted to share something I've been working on for a while: SOFA HRTF audio samples for comparison: https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc It's part of a broader project that aims to introduce people to binaural audio. More info here: https://kutt.it/binaural I'm open to any feedback. 1f8ea66677e0f1af83b61034d845852c5b4cf254 2351 2346 2021-06-28T11:56:39Z Isfmiho 3 wikitext text/x-wiki == 3D3A LAB Database == Hello! Is there a specific reason the 3D3A LAB Database is not present in the SOFA repository? here is a link to the dataset: https://www.princeton.edu/3D3A/HRTFMeasurements.html I hope I'm using this tool correctly. Best, == Binaural Audio database == Greetings, I just wanted to share something I've been working on for a while: SOFA HRTF audio samples for comparison: https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc It's part of a broader project that aims to introduce people to binaural audio. More info here: https://kutt.it/binaural I'm open to any feedback. == Adding Databases == Hello, my name is Michael, both of you should have received an email via the mediawiki page. I can offer you my support to add the databases to the repository. If you did not receive my email please contact me via email: [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA People behind SOFA] Best regards, Michael Mihocic f34b7ceb6276e10837e6e82339e35221f6abd18b 0 16 2349 2196 2021-06-28T09:12:40Z Isfmiho 3 wikitext text/x-wiki * '''[https://www.oeaw.ac.at/en/ari/our-team/majdak-piotr Piotr Majdak]''' ([https://www.oeaw.ac.at/en/ari/ Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader, Matlab support * '''[https://www.noisternig.com/ Markus Noisternig]''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[https://www.qu.tu-berlin.de/menue/team/alumni/hagen_wierstorf/ Hagen Wierstorf]''' ([https://www.qu.tu-berlin.de/menue/qu/ Quality and Usability Lab], [http://www.tu-berlin.de/ Technical University of Berlin]): Octave support * '''[https://www.oeaw.ac.at/en/ari/our-team/mihocic-michael Michael Mihocic]''' ([https://www.oeaw.ac.at/en/ari/ Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Website support * '''Harald Ziegelwanger''' ([https://www.oeaw.ac.at/en/ari/ Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ API, specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): initiation of the [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) * '''Yukio Iwaya''' (Faculty of Engineering, Tohoku Gakuin University) * '''Michele Geronazzo''' (University of Padova): headphone support Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You need to be a member of the mailing list to send a message to the list. You don't need to be a member to send an email to the moderator. Also you are invited to contact the standardization committee of X212. Join us at [http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. afba469c79660282451a7f207a45cbeebf9d5409 0 15 2352 2165 2021-07-02T12:16:52Z Isfmiho 3 wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Kutt == The [https://kutt.it/binaural Kutt project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. 3fccc8ca304e666c51517f11df10c6eeb629327a 0 1 2353 2328 2021-07-02T12:27:19Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 02.07.2021: Application Kutt added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 4b70e337d95c0eb8320d15fcf3890fd0de51ee90 2355 2353 2021-07-06T07:09:06Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 3fab71bc41c7a76e2eca52b9c58e009096e8b674 2391 2355 2021-10-11T12:49:11Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 893786b7b6d41988d68e866283cc12c14c1cee74 2396 2391 2021-10-19T05:26:09Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 19.10.2021: 3D3A, HRTFs from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 2d2a5123e3c83b350e91e433ebce642660fb9ed4 2399 2396 2021-10-19T06:00:47Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released b7aa33c5653fec04784069188303b311ffe861ea 0 15 2354 2352 2021-07-06T07:08:45Z Isfmiho 3 /* Application: Kutt */ wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. 992ddd6cee77efba4cbdae9aa72807e3411c7b5e 2390 2354 2021-10-11T12:48:39Z Isfmiho 3 wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria in Brazil and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. 57988f291e45ed8fde99118996c948a341ed5037 2 543 2356 2337 2021-07-09T02:49:26Z 3DJ 961 wikitext text/x-wiki Binaural audio enthusiast working on some projects: https://kutt.it/Binaural - Binaural audio intro https://kutt.it/BinauralDatabase - Binaural database (configurations, demos, ratings, guides, etc.) https://kutt.it/BinauralDatabaseSearch - Binaural database search engine https://kutt.it/BinauralDatabaseCatalog - Binaural database guide showcase https://kutt.it/BinauralDatabaseAdd - Report and review binaural audio in games/programs/websites/music/movies/etc. https://kutt.it/BinauralSoftware - Binaural audio software https://kutt.it/BinauralHRTF - Binaural profile (HRTF) sample database for comparison https://kutt.it/BinauralResources - Misc. resources https://kutt.it/BinauralExperiments - Binaural audio experiments 0226f7e7fc864b067299cedcfcddf5aa25a88d2e 2357 2356 2021-07-09T02:49:43Z 3DJ 961 wikitext text/x-wiki Binaural audio enthusiast working on some projects: https://kutt.it/Binaural - Binaural audio intro https://kutt.it/BinauralDatabase - Binaural database (configurations, demos, ratings, guides, etc.) https://kutt.it/BinauralDatabaseSearch - Binaural database search engine https://kutt.it/BinauralDatabaseCatalog - Binaural database guide showcase https://kutt.it/BinauralDatabaseAdd - Report and review binaural audio in games/programs/websites/music/movies/etc. https://kutt.it/BinauralSoftware - Binaural audio software https://kutt.it/BinauralHRTF - Binaural profile (HRTF) sample database for comparison https://kutt.it/BinauralResources - Misc. resources https://kutt.it/BinauralExperiments - Binaural audio experiments 423f605b629cbed0f265c32f04ed353ceabfe340 0 498 2358 2315 2021-08-04T09:56:51Z Fbrinkmann 748 wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki></nowiki>||||IS, MS||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||MS||attribute||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded and will be called "FreeFieldDirectivityTF" from version 1.0 again (according to SOFA standard). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 8e3dd8d5a878e5bd89e9c6271bff095762fb5ab7 2373 2358 2021-10-05T08:48:15Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or '2-way loudspeaker' |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or 'LoudspeakerCompany' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, 'The bell'. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, 'Viewing direction of the bell'. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, 'Along the keys, keys up'. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki>{''}</nowiki>||||IS, MS||string||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki>{''}</nowiki>||||MS||string||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki>440</nowiki>||||I, M||double||Frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded and will be called "FreeFieldDirectivityTF" from version 1.0 again (according to SOFA standard). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 75f50523587b34b589cac799694c8a98f5c318ab 0 5 2359 2310 2021-10-05T07:40:19Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of SimpleFreeFieldHRIR in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 5e73b03c4e3ec41589670afc09eabbac520ad2c5 2360 2359 2021-10-05T07:41:23Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! e3a09318b5a8afdd569a302f5f900924cddd3aec 2363 2360 2021-10-05T08:40:16Z Isfmiho 3 /* Stable SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: Binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 9a071bd56a2bda22b5134b3e459f3e60cf30475f 2389 2363 2021-10-05T09:21:13Z Isfmiho 3 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: Binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 8c40fd14fe15aa711cc6a1b46d2dbb65d4daa472 0 549 2361 2021-10-05T08:11:33Z Isfmiho 3 Created page with "The convention is an extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction cor..." wikitext text/x-wiki The convention is an extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter (instead of a source position), and a consistent measurement for a single listener and all directions is described by a set of the emitter positions (instead of source positions) surrounding the listener. The data type 'FIR-E' is used (instead of 'FIR' as in [[SimpleFreeFieldHRIR]]). The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldHRIR</nowiki>||rm||||attribute||An extension of SimpleFreeFieldHRIR in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Source position is assumed to be the ListenerPosition in order to reflect Emitters surrounding the Listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Radius in 'spherical harmonics', Position in 'cartesian' and 'spherical' |- |EmitterPosition:Type||<nowiki>spherical harmonics</nowiki>||m||||attribute||Can be 'spherical harmonics', 'cartesian', or 'spherical' |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mrne||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRNE||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||||||attribute|| |} 9b536439e94d4201d4d23e29a9f70415f6f25e41 2392 2361 2021-10-14T15:29:44Z Isfmiho 3 wikitext text/x-wiki The convention is an extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter (instead of a source position), and a consistent measurement for a single listener and all directions is described by a set of the emitter positions (instead of source positions) surrounding the listener. The data type 'FIR-E' is used (instead of 'FIR' as in [[SimpleFreeFieldHRIR]]). The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldHRIR</nowiki>||rm||||attribute||An extension of SimpleFreeFieldHRIR in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Source position is assumed to be the ListenerPosition in order to reflect Emitters surrounding the Listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Radius in 'spherical harmonics', Position in 'cartesian' and 'spherical' |- |EmitterPosition:Type||<nowiki>spherical harmonics</nowiki>||m||||attribute||Can be 'spherical harmonics', 'cartesian', or 'spherical' |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mrne||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 73bad2a6c6437cd4cad5bce6a0d01ddfefdc7b1a 0 538 2362 2272 2021-10-05T08:13:12Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldHRTF</nowiki>||rm||||attribute||This conventions is for HRTFs created under conditions where room information is irrelevant and stored as SH coefficients |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Source position is assumed to be the ListenerPosition in order to reflect Emitters surrounding the Listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Radius in 'spherical harmonics', Position in 'cartesian' and 'spherical' |- |EmitterPosition:Type||<nowiki>spherical harmonics</nowiki>||m||||attribute||Can be 'spherical harmonics', 'cartesian', or 'spherical' |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mrne||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRNE||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||||||attribute|| |} 40642c36f1511aab1a66b72ec39478f76ba4f27b 0 550 2364 2021-10-05T08:41:23Z Isfmiho 3 Created page with "Conventions for testing the string support. Version 0.2 included in SOFA 1.0. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] !SOFA_conventions#AnchorD..." wikitext text/x-wiki Conventions for testing the string support. Version 0.2 included in SOFA 1.0. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralString</nowiki>||rm||||attribute||Conventions for testing the string support |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>String</nowiki>||rm||||attribute||We store strings here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |String2||<nowiki>{'' ''}</nowiki>||m||MRS||string|| |- |String2:Description||<nowiki>2-D string</nowiki>||m||||attribute|| |- |String2:Units||<nowiki>latin1</nowiki>||m||||attribute|| |- |Data.String1||<nowiki>{''}</nowiki>||m||MS||string|| |- |Data.String1:Description||<nowiki>1-D string</nowiki>||m||||attribute|| |- |Data.String1:Units||<nowiki>latin1</nowiki>||m||||attribute|| |- |Data.String2||<nowiki>{'' ''}</nowiki>||m||MRS||string|| |- |Data.String2:Description||<nowiki>2-D string</nowiki>||m||||attribute|| |- |Data.String2:Units||<nowiki>latin1</nowiki>||m||||attribute|| |- |Data.Double||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.Double:Units||<nowiki>double</nowiki>||m||||attribute|| |} 9447e27fa8994f1528efa5f9894554c6992cec79 0 286 2365 2291 2021-10-05T08:43:27Z Isfmiho 3 wikitext text/x-wiki This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} b61f2ddf2806f9b5781f7e78128d650eccc30fea 2384 2365 2021-10-05T09:18:39Z Isfmiho 3 wikitext text/x-wiki __TOC__ == Description == This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} == Version 1.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} 8ff62c9ec07f0a7ac743c9276c21468e842d8f8a 2385 2384 2021-10-05T09:19:04Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki __TOC__ == Description == This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} == Version 1.0 == Version 1.0 is deprecated. Please use Conventions version 2.0 instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} 9b33698a6b1365dc2a9796ab7cc27a5c6b1c662f 0 287 2366 1965 2021-10-05T08:44:09Z Isfmiho 3 GeneralTF conventions wikitext text/x-wiki This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} d41887c585fb67eee3758f34a9105fd4a50376a2 2378 2366 2021-10-05T08:50:57Z Isfmiho 3 wikitext text/x-wiki This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 8f05872dd3b7d374e79eb616849a0f032e738181 2379 2378 2021-10-05T08:52:21Z Isfmiho 3 wikitext text/x-wiki ==Description== This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 8c040f7e585d3733593faed7ce022876c45058de 2380 2379 2021-10-05T08:55:37Z Isfmiho 3 /* Version 2.0 */ wikitext text/x-wiki ==Description== This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == The conventions version 2.0 is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} fa7f2d7dbe219418bf5f0f7d4ed38fd04c76bfab 2381 2380 2021-10-05T08:56:11Z Isfmiho 3 /* Version 2.0 */ wikitext text/x-wiki ==Description== This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 8c040f7e585d3733593faed7ce022876c45058de 2382 2381 2021-10-05T08:56:45Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki ==Description== This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == Version 1.0 is deprecated. Please use Conventions version 2.0 instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 760ce229b00564886ac0e4509745151faf7faf8a 2383 2382 2021-10-05T09:16:54Z Isfmiho 3 wikitext text/x-wiki __TOC__ ==Description== This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == Version 1.0 is deprecated. Please use Conventions version 2.0 instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 182f3234e50ffbdefcbb2b94c62d81014ee26d0d 0 9 2367 2163 2021-10-05T08:45:07Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.4, we use SourcePosition to represent the different HRTF directions. By doing so, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the last version before AES69-2015, we adapted the conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). SimpleFreeFieldHRIR version 1.0 represents the current standardized convention set from AES69-2015. == Version 1.0 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This convention set essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This convention set can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 H 0; 0 -H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRIR</nowiki>||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||||||attribute|| |} == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Version 0.4 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 14149092005ce100a2d23f1ffac7ce773bb5d51d 0 531 2368 2265 2021-10-05T08:45:37Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed [[GeneralFIR]] convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR-E</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, EC, ECM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrne||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} 3e6a2e91fab4e819c6cfec71aaf59b0c5935f025 0 533 2369 2266 2021-10-05T08:46:01Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends [[GeneralTF]] by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF-E</nowiki>||rm||||attribute||This conventions stores TFs depending in the Emiiter for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralTF |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute||We store frequency-dependent data depending on the emitter here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, EC, ECM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrne||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 1025ca21472a17daf6ffcc893e886fac80b84b0e 0 534 2370 2260 2021-10-05T08:46:17Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with any datatype (no restrictions at all). The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>General</nowiki>||rm||||attribute||This conventions is for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||m||||attribute||The datatype can be arbitrary |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmiiterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |} c52297924ae638c9e1f9914c2570fed690c0cb9c 0 535 2371 2261 2021-10-05T08:46:39Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is TF. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRTF</nowiki>||rm||||attribute||This conventions is for HRTFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||||||attribute|| |} 388a0b68daf500f767f2313fa533fe0a0ba6faf1 0 532 2372 2281 2021-10-05T08:46:59Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is SOS. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} fa579327ce440756f26cfadbecc4c8c120608527 0 536 2374 2282 2021-10-05T08:48:34Z Isfmiho 3 wikitext text/x-wiki This conventions defines spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |} b64bd740ce5702820caed6ce700f6711afc6ae81 2393 2374 2021-10-14T15:32:01Z Isfmiho 3 wikitext text/x-wiki {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute||Type of coordinate system for RoomCornerA and RoomCornerB |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute||Unit of coordinate system for RoomCornerA and RoomCornerB |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |} a67be6bd9b20ab637e9afb9f867d007b93df47a1 0 537 2375 2264 2021-10-05T08:48:57Z Isfmiho 3 wikitext text/x-wiki This conventions defines SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomMIMOSRIR</nowiki>||rm||||attribute||Single-room multiple-input multiple-output spatial room impulse responses, depending on Emitters |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute||Shall be FIR-E |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrne||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRI, MRI, MRE||double||Additional delay of each IR (in samples) |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||m||IC, MC||double|| |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |} 2fbcb6d78c9b80dcfd2ac3c21ee8ce730d62229c 0 459 2376 2270 2021-10-05T08:49:15Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.2.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Version 0.2 === This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} === Version 0.1, previously proposed as HeadphoneIR (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} 42138673fe6b7157c2bd00916e920802b09a95d6 0 477 2377 1972 2021-10-05T08:49:39Z Isfmiho 3 /* Version 0.3 */ wikitext text/x-wiki ==Description== [[File:MultiSpeakerBRIR-0.3.png|right|thumb|225px]] This conventions was developed for binaural room impulse responses (BRIRs) measured in a multispeaker setup (=multiple emitters). It is based on SimpleFreeFieldHRIR with the most striking difference of using the '''FIRE''' as DataType. This allows to more compactly describe the data for all involved emitters. == Version 0.3 == This version uses SOFA 1.0 which reflects the standard AES69-2015. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} == Old deprecated versions == === Version 0.2 === In this version, we explicitly use the Datatype FIRE. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double|| |} === Version 0.1 === This was the first version, it used FIR datatype which was inofficially extended by E. Also, the comment said that EmitterPosition determines the size of E, which is deprecated as well. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>MultiSpeakerBRIR</nowiki>||rm||||attribute||This convention is for BRIRs recorded in reverberant conditions from multiple loudspeaker sources at a number of listener orientations. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double||When EmitterUp provided, EmitterView must be provided as well |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double||When EmitterView provided, EmitterUp must be provided as well |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>meter</nowiki>||||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |} b6fe47d0d06a9ff02b8b4590a606b5ef529d7ea9 0 478 2386 1967 2021-10-05T09:19:53Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[GeneralFIR]]. The only difference is the DataType, which is FIR'''E''', not FIR. All other attributes and variables follow the general SOFA specifications. As GeneralFIR, this convention set can be used to save data which are too general to store in more specific conventions. == Version 1.0 == This version follows the conventions [[GeneralFIR]] (version 1.0) standardized in AES69-2015. Note that GeneralFIRE 1.0, in contrast to GeneralFIR 1.0, has not been included in the standard, thus, here, we declare it as stable. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} b3ef53f065061ac50855f4815e813c0118ad46f3 0 476 2387 2287 2021-10-05T09:20:25Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[SimpleFreeFieldHRIR]]. The only difference is the DataType, which is [http://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#SOS_.28proposed.29 SOS], not FIR. SimpleFreeFieldSOS was requested to cover the needs coming from fast HRTF rendering, where an HRTF is represented as a broadband delay and small number of second-order sections (SOSs). It is recommended to use [[SimpleFreeFieldHRSOS]] instead, which is defined in AES69-2020 (SOFA 2.0). == Version 1.0 == This version follows the conventions SimpleFreeFieldHRIR (version 1.0) standardized in AES69-2015. Note: * In contrast to SimpleFreeFieldHRIR 1.0, SimpleFreeFieldSOS 1.0 has not been included in the standard. But it can be considered as stable. * SimpleFreeFieldSOS does not impose any restriction on the filter coefficients contained in Data.SOS. Especially it is the user responsibility to check whether the filters are stable or not. * We encourage to provide information in 'History' about the creation of SOSs and estimation of delay from the underlying filters. * We further encourage to use 'Parents' can be used to link the SimpleFreeFieldSOS file with the file containing the original filters. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} 3d4e8137b77e668d1f272ea167bdb2438dfab77f 0 25 2388 1971 2021-10-05T09:20:54Z Isfmiho 3 /* Version 0.3 */ wikitext text/x-wiki ==Description== [[File:SingleRoomDRIR.png|right|thumb|225px]] This convention set defines a setup used for measuring DRIRs in a single room with a single excitation source and a microphone array containing an arbitrary number of omnidirectional microphones (i.e., receivers). The positions of both the source and the listener are considered as variant. The DRIRs are represented as FIR filters for a single room per file. SingleRoomDRIR consists of: * General metadata: RoomType: revereberant with a mandatory global attribute RoomDescription. * Data: Datatype: FIR, the amount of the receivers varies, thus, the size of Data.IR is [M R N]. * Source: The position and the orientation of the source may vary and is given by SourcePosition, SourceUp, and SourceView. The coordinate type is cartesian and unit is meter. * Emitters: Source consists of a single omnidirectional emitter, which position is fixed, EmitterPosition: (0 0 0). EmitterUp and EmitterView are optional. * Listener: Position and the orientation of the listener vary and thus ListenerPosition, ListenerView, and ListenerUp are mandatory. The coordinate type is cartesian and unit is meter. An additional rotation of the listener is can be considered, thus, ListenerRotation is optional. * Receivers: the position of all receivers via ReceiverPosition is provided. The coordinate type is cartesian and unit is meter. The receivers are considered to be omnidirectional, thus, ReceiverUp and ReceiverView are omitted. == Version 0.3 == This version uses SOFA 1.0 which reflects the standard AES69-2015. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomDRIR</nowiki>||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.3</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>reverberant</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView||<nowiki>[-1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0]</nowiki>||m||mrn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0]</nowiki>||m||IR, MR||double|| |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SingleRoomDRIR||rm||||attribute||This convention stores arbitrary number of receivers while providing an information about the room. The main application is to store DRIRs for a single room. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||reverberant||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 0 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition:Type||cartesian||m||||attribute|| |- |SourcePosition:Units||meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute|| |- |GLOBAL:RoomDescription||||m||||attribute|| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |SourceUp||[0 0 1]||m||IC, MC||double|| |- |SourceView||[-1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} 34b7dcec7e2c2f56715523fc540b26edac73847c 0 17 2394 2350 2021-10-19T05:23:30Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs of 38 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 8c06eda349552a37efb8fa47baab778a84fe0e17 2395 2394 2021-10-19T05:23:59Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs of 38 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 054caaefa442899928a54d23d83f5501d3cc30a0 2397 2395 2021-10-19T05:31:00Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 30d626ae65647c00d6e5ea7ae499d0feaf88d9db 2398 2397 2021-10-19T06:00:36Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans for 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 3eb32c9480f792484b8ef178230887838ce67c68 2400 2398 2021-10-19T06:01:07Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially antropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 4e41569237b6bcfa3a9952b2d0ba7338937c781b 1 463 2401 2351 2021-10-24T08:03:48Z 3DJ 961 /* 3D3A LAB HRTF not formatted properly? */ new section wikitext text/x-wiki == 3D3A LAB Database == Hello! Is there a specific reason the 3D3A LAB Database is not present in the SOFA repository? here is a link to the dataset: https://www.princeton.edu/3D3A/HRTFMeasurements.html I hope I'm using this tool correctly. Best, == Binaural Audio database == Greetings, I just wanted to share something I've been working on for a while: SOFA HRTF audio samples for comparison: https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc It's part of a broader project that aims to introduce people to binaural audio. More info here: https://kutt.it/binaural I'm open to any feedback. == Adding Databases == Hello, my name is Michael, both of you should have received an email via the mediawiki page. I can offer you my support to add the databases to the repository. If you did not receive my email please contact me via email: [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA People behind SOFA] Best regards, Michael Mihocic == 3D3A LAB HRTF not formatted properly? == Greetings, I'm trying to [https://github.com/ThreeDeeJay/HRIR-Batch-Converters convert] the recently released 3D3A Lab HRTFs to [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV format so I can generate demo samples for the [https://kutt.it/BinauralHRTF HRTF database], but I'm running into [https://i.imgur.com/F4hbGlf.png errors] during conversion. They also fail to [https://i.imgur.com/tDVM2Yr.png load in the Anaglyph VST plugin]. Most HRTFs like IRCAM work properly in both cases. although I get the same errors with [https://sofacoustics.org/data/database_sofa_0.5/listen/ IRCAM Listen v0.5] so perhaps the problematic ones are just using an outdated format. And speaking of, is there a reason the [http://recherche.ircam.fr/equipes/salles/listen/ IRCAM Listen] HRTFs aren't listed on the Wiki, even though the files are [https://sofacoustics.org/data/database/listen/ already hosted]? 061db26a7a72d883c92fdd1fdf532618168568aa 2402 2401 2021-10-24T08:24:45Z 3DJ 961 /* 3D3A LAB HRTF not formatted properly? */ wikitext text/x-wiki == 3D3A LAB Database == Hello! Is there a specific reason the 3D3A LAB Database is not present in the SOFA repository? here is a link to the dataset: https://www.princeton.edu/3D3A/HRTFMeasurements.html I hope I'm using this tool correctly. Best, == Binaural Audio database == Greetings, I just wanted to share something I've been working on for a while: SOFA HRTF audio samples for comparison: https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc It's part of a broader project that aims to introduce people to binaural audio. More info here: https://kutt.it/binaural I'm open to any feedback. == Adding Databases == Hello, my name is Michael, both of you should have received an email via the mediawiki page. I can offer you my support to add the databases to the repository. If you did not receive my email please contact me via email: [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA People behind SOFA] Best regards, Michael Mihocic == 3D3A LAB HRTF not formatted properly? == Greetings, I'm trying to [https://github.com/ThreeDeeJay/HRIR-Batch-Converters convert] the recently released 3D3A Lab HRTFs to [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV format so I can generate demo samples for the [https://kutt.it/BinauralHRTF HRTF database], but I'm running into [https://i.imgur.com/F4hbGlf.png errors] during conversion. They also fail to [https://i.imgur.com/tDVM2Yr.png load in the Anaglyph VST plugin]. Most HRTFs like IRCAM work properly in both cases. although I get the same errors with [https://sofacoustics.org/data/database_sofa_0.5/listen/ IRCAM Listen v0.5] so perhaps the problematic ones are just using an outdated format. And speaking of, is there a reason the [http://recherche.ircam.fr/equipes/salles/listen/ IRCAM Listen] HRTFs aren't listed on the Wiki, even though the files are [https://sofacoustics.org/data/database/listen/ already hosted]? P.S. I also tested the other versions available [http://gofile.me/6GzJ0/67b2jfkjw here], but the issue still persists. Perhaps I should try contacting them directly. 27b4c2e7254f9594434c1ac41052d4f52528bf74 0 15 2403 2390 2021-10-27T07:35:18Z Isfmiho 3 wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows to browse through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. ed3634e28a15ffc701711c137a9a2f308886d928 2407 2403 2021-10-29T09:26:33Z Isfmiho 3 /* HDF5View: Generic SOFA file viewer */ wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. 1c35827920a79a4ceda1aa79f8075e8b5d004116 2408 2407 2021-10-29T09:30:09Z Isfmiho 3 /* pySOFA: Lightweight SOFA API for Python (read only, FIR only) */ wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read-only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. b026640ab79aaa93a4a2213941c6142556a014b0 2414 2408 2021-11-02T10:35:12Z Isfmiho 3 wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read-only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == sofar: Maybe the most complete Python package for the SOFA file format (read/write support) == [https://pypi.org/project/sofar/ sofar] is a SOFA API for Python made by Fabian Brinkmann. It supports both reading and writing of SOFA files. The API allows adding custom attributes to SOFA files and verifying its content with respect to the data type and shape. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. d75630205373259f1d55ec220ab6fb0bb1832bd4 2416 2414 2021-11-10T06:08:51Z Isfmiho 3 /* sofar: Maybe the most complete Python package for the SOFA file format (read/write support) */ wikitext text/x-wiki == HDF5View: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read-only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == sofar: Maybe the most complete Python package for the SOFA file format (read/write support) == [https://pypi.org/project/sofar/ sofar] is a SOFA API for Python made by Fabian Brinkmann. It supports both reading and writing of SOFA files. The API allows adding custom data & attributes to SOFA files and verifying its content with respect to the data type and shape. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. 3e7dd21d3a6e26991997cf5990b10e0a2caf9664 2419 2416 2021-12-13T07:59:09Z Isfmiho 3 /* HDFView: Generic SOFA file viewer */ wikitext text/x-wiki == HDFView: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read-only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == sofar: Maybe the most complete Python package for the SOFA file format (read/write support) == [https://pypi.org/project/sofar/ sofar] is a SOFA API for Python made by Fabian Brinkmann. It supports both reading and writing of SOFA files. The API allows adding custom data & attributes to SOFA files and verifying its content with respect to the data type and shape. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: WaveCloud-M == [http://www.ee.bgu.ac.il/~sheaffer/wavecloud.html WaveCloud-M] is Matlab-oriented room simulator. Beginning with version 1.0, WaveCloud-M can use HRTFs saved in SOFA to render binaural signals. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. 7f86af3bd86539bc75055fa4bc85f568a3f5205a 2421 2419 2021-12-14T06:45:24Z Isfmiho 3 list of SOFA software, tools, and APIs wikitext text/x-wiki == HDFView: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read-only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == sofar: Maybe the most complete Python package for the SOFA file format (read/write support) == [https://pypi.org/project/sofar/ sofar] is a SOFA API for Python made by Fabian Brinkmann. It supports both reading and writing of SOFA files. The API allows adding custom data & attributes to SOFA files and verifying its content with respect to the data type and shape. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. 05d768b5aae830a80d19a19521caec0b25571710 2441 2421 2022-04-21T11:40:54Z Noisternig 5 wikitext text/x-wiki == HDFView: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read-only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == sofar: Maybe the most complete Python package for the SOFA file format (read/write support) == [https://pypi.org/project/sofar/ sofar] is a SOFA API for Python made by Fabian Brinkmann. It supports both reading and writing of SOFA files. The API allows adding custom data & attributes to SOFA files and verifying its content with respect to the data type and shape. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: IRCAM Spat == [http://forumnet.ircam.fr/product/spat-en/ Spat] is a software suite for spatialization of sound signals in real-time intended for musical creation, postproduction, and live performances made by IRCAM. It supports SOFA for binaural rendering. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. 4f6cb1bf19293e247350d8b5bc72c573e6a1fb6e 2442 2441 2022-04-21T11:44:46Z Noisternig 5 wikitext text/x-wiki == HDFView: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA API for Matlab/Octave == SOFA API for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read-only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == sofar: Maybe the most complete Python package for the SOFA file format (read/write support) == [https://pypi.org/project/sofar/ sofar] is a SOFA API for Python made by Fabian Brinkmann. It supports both reading and writing of SOFA files. The API allows adding custom data & attributes to SOFA files and verifying its content with respect to the data type and shape. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: IRCAM Spat == [https://forum.ircam.fr/projects/detail/spat/ Spat] is a software suite for sound spatialisation in real-time in music creation, post-production, and live performances. It supports SOFA for binaural rendering. == Application: IRCAM Panoramix == [https://forum.ircam.fr/projects/detail/panoramix/ Panoramix] is a standalone application for spatial audio mixing and post-production. It supports SOFA for binaural rendering. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. 18687f851671be3264788bcf3898715563d43a1c 0 1 2404 2399 2021-10-27T07:36:33Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 3613e68c0817ec20e93f737d3eea60b1104e6d38 2415 2404 2021-11-02T10:39:13Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released ac53f92e21f06c411aa6ad02f2903584e6e0f125 2422 2415 2021-12-14T06:47:09Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released f1d1990e045e01f882d466f656b4f728aa743c2c 2426 2422 2021-12-28T09:09:01Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 4a370bb993bfd0f563c4491f72fbb55fc17259a9 2428 2426 2021-12-28T10:23:25Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 28.12.2021: SADIE database added (Credit: Gavin Kearney, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 4bdbad08b473a997e3d3db569d5e718f6a7ad883 2429 2428 2021-12-28T11:52:56Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 39ca64ad8c12ea7d6d0c563c28f80d6f3b51804d 2434 2429 2022-01-05T10:35:17Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released f25bfa98394ec80bad8064e2f79c325bb6120414 2443 2434 2022-05-05T09:31:06Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released ff340d304c01165c5cce320af0bff274c204fd99 2451 2443 2022-07-18T08:29:00Z Petibub 4 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 9cf794b4d1768a99136ed4f493eac783a4539481 1 463 2405 2402 2021-10-27T07:49:49Z Isfmiho 3 wikitext text/x-wiki (fixed issues removed from this site) == 3D3A LAB HRTF not formatted properly? == Greetings, I'm trying to [https://github.com/ThreeDeeJay/HRIR-Batch-Converters convert] the recently released 3D3A Lab HRTFs to [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV format so I can generate demo samples for the [https://kutt.it/BinauralHRTF HRTF database], but I'm running into [https://i.imgur.com/F4hbGlf.png errors] during conversion. They also fail to [https://i.imgur.com/tDVM2Yr.png load in the Anaglyph VST plugin]. Most HRTFs like IRCAM work properly in both cases. although I get the same errors with [https://sofacoustics.org/data/database_sofa_0.5/listen/ IRCAM Listen v0.5] so perhaps the problematic ones are just using an outdated format. And speaking of, is there a reason the [http://recherche.ircam.fr/equipes/salles/listen/ IRCAM Listen] HRTFs aren't listed on the Wiki, even though the files are [https://sofacoustics.org/data/database/listen/ already hosted]? P.S. I also tested the other versions available [http://gofile.me/6GzJ0/67b2jfkjw here], but the issue still persists. Perhaps I should try contacting them directly. >> Michael: I tried to load the 3D3A SOFA files and they seem to load properly. I will forward the issue of the converter to the author. I will also check the IRCAM Listen issue. Thanks for pointing it out! 6bf0748b1e4ec81b3f98979dc1558627abc52a69 2425 2405 2021-12-28T09:08:04Z Isfmiho 3 /* 3D3A LAB HRTF not formatted properly? */ wikitext text/x-wiki (fixed issues removed from this site) == 3D3A LAB HRTF not formatted properly? == Greetings, I'm trying to [https://github.com/ThreeDeeJay/HRIR-Batch-Converters convert] the recently released 3D3A Lab HRTFs to [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV format so I can generate demo samples for the [https://kutt.it/BinauralHRTF HRTF database], but I'm running into [https://i.imgur.com/F4hbGlf.png errors] during conversion. They also fail to [https://i.imgur.com/tDVM2Yr.png load in the Anaglyph VST plugin]. Most HRTFs like IRCAM work properly in both cases. although I get the same errors with [https://sofacoustics.org/data/database_sofa_0.5/listen/ IRCAM Listen v0.5] so perhaps the problematic ones are just using an outdated format. And speaking of, is there a reason the [http://recherche.ircam.fr/equipes/salles/listen/ IRCAM Listen] HRTFs aren't listed on the Wiki, even though the files are [https://sofacoustics.org/data/database/listen/ already hosted]? P.S. I also tested the other versions available [http://gofile.me/6GzJ0/67b2jfkjw here], but the issue still persists. Perhaps I should try contacting them directly. >> Michael: I tried to load the 3D3A SOFA files and they seem to load properly. I will forward the issue of the converter to the author. >> Michael: Listen data are added to the database (should be visible by tomorrow). 703ba3baeb4ceedd90d0a7b4a77517e3ff28c9fd 0 537 2406 2375 2021-10-28T12:08:15Z Isfmiho 3 SingleRoomMIMOSRIR conventions wikitext text/x-wiki This conventions defines SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of receivers (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomMIMOSRIR</nowiki>||rm||||attribute||Single-room multiple-input multiple-output spatial room impulse responses, depending on Emitters |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute||Shall be FIR-E |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrne||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRI, MRI, MRE||double||Additional delay of each IR (in samples) |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||m||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |} a6952cc52d812de3f9b5a259dbde59b45e8d62d6 2435 2406 2022-02-08T08:46:55Z Fbrinkmann 748 wikitext text/x-wiki This conventions defines SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomMIMOSRIR</nowiki>||rm||||attribute||Single-room multiple-input multiple-output spatial room impulse responses, depending on Emitters |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute||Shall be FIR-E |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrne||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRI, MRI, MRE||double||Additional delay of each IR (in samples) |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||m||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |} 92579f638410ef1496b82113adf37b2a7d1f7ddf 0 17 2409 2400 2021-10-29T09:50:51Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 8c5f0ca59804173e9ab5f272a71c98ff16d92bfb 2410 2409 2021-10-29T09:51:33Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropomeric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 9c0840640dc3e6444cf965027942bef4955511ff 2411 2410 2021-10-29T09:52:07Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)] HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. a1f27a5c3a8e8a4cc45fe78ab34a3fbfbef060cc 2412 2411 2021-10-29T09:56:02Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspekears, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 470eabe1cc890a36239afddf2507e6eb1576de69 2413 2412 2021-10-29T10:17:48Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 5eca41f82923ca0c71578f699c45ebb4950f334d 2417 2413 2021-12-07T08:14:12Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * '''RIEC database''': Database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan. Link: http://www.riec.tohoku.ac.jp/pub/hrtf/index.html * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. dd854dc320ab32705dc7c7f09027f4f0fa1d62ed 2418 2417 2021-12-07T08:14:26Z Isfmiho 3 /* Other repositories */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [http://interface.cipic.ucdavis.edu/data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 6a26c97da1bcad6ab11f8bb3b38801d3c84c84da 2420 2418 2021-12-13T08:53:01Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * '''New: [https://sofacoustics.org/data/database/3d3a/ 3D3A]''': Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * '''New: [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:]''' High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 87a5c4948ea12765e38948606af5647a6afdc5f8 2423 2420 2021-12-28T08:34:14Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ BiLi project]. ''(Credit: Markus Noisternig, Paris)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 9db3a3867a59fe6fe0a9485ab0959e9e5c28fbb3 2424 2423 2021-12-28T08:47:05Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]''': Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]''': Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 7c9bc68c6ad7ff5ddcd2b4049d12981fc51f920f 2427 2424 2021-12-28T10:20:44Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]''': Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]''': Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. e564428f12b20064e8511ee17642b772ff88ada2 2430 2427 2021-12-28T11:53:10Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]''': Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]''': Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 864210f5568a3a721a66df445521f6c131a3793b 2431 2430 2021-12-28T12:03:25Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]''': Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]''': Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. f65214b83978e8dda51e75e3e3995be338610faf 2432 2431 2021-12-28T13:37:16Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]''': Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]''': Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 1653cba90c3f7dcb94bffee59a1edd12f8c73240 2433 2432 2022-01-05T10:35:03Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]''': Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]''': Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 7076f634c50f6e48772fe33510e26526ddfc3fe2 2447 2433 2022-07-01T08:36:24Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially anthropometric data available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]''': Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]''': Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/sadie/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 2a1e68dbf33d518732574bc4ca85eddfbfe0ec42 2450 2447 2022-07-18T08:25:14Z Petibub 4 CIPIC: Link to a local copy of anthropometric data added wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * '''New: [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]''': Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]''': Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]''': Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * '''New: [https://sofacoustics.org/data/database/sadie/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 5546b406408bdb4b34611db9c0adcbe0b4feb001 2452 2450 2022-07-18T12:08:01Z Petibub 4 SCUT: Near-field HRTFs with anthropometric data wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs with anthropometric data (see CSV and PDF). ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. e705b4018bbc599de83309b1b69ba85a90526f93 0 5 2436 2389 2022-02-08T08:47:22Z Fbrinkmann 748 wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: Binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 50814f56838a469e4ac43710d67613f71612ebe5 2439 2436 2022-04-12T12:12:25Z Isfmiho 3 /* Deprecated SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[MultiSpeakerBRIR]]: Binaural room impulse responses (BRIRs) measured with an arbitrary number of ''emitters'' (such as a loudspeaker array). * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 78536833a960dc941f8d3754e4b8268ca8211258 2440 2439 2022-04-12T12:12:47Z Isfmiho 3 /* Stable SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[MultiSpeakerBRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 73f40630123eee01f7d3e4b773869a674b29b240 2444 2440 2022-05-25T11:40:32Z Isfmiho 3 /* Deprecated SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! a86d5461c08162cd6adfc39f4c38b6eeb221a3cc 0 538 2437 2362 2022-02-14T07:06:44Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldHRTF</nowiki>||rm||||attribute||This conventions is for HRTFs created under conditions where room information is irrelevant and stored as SH coefficients |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Source position is assumed to be the ListenerPosition in order to reflect Emitters surrounding the Listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Radius in 'spherical harmonics', Position in 'cartesian' and 'spherical' |- |EmitterPosition:Type||<nowiki>spherical harmonics</nowiki>||m||||attribute||Can be 'spherical harmonics', 'cartesian', or 'spherical' |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mrne||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRNE||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute|| |} 8aab9677c2f1a6e7649132583d843c31e6766d50 0 535 2438 2371 2022-02-14T07:07:05Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is TF. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRTF</nowiki>||rm||||attribute||This conventions is for HRTFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N:LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute|| |} 902ea44a73ae2bd7ee9d5ef11f4f7bef9af03d66 0 536 2445 2393 2022-05-30T12:05:20Z Isfmiho 3 wikitext text/x-wiki Spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute||Type of coordinate system for RoomCornerA and RoomCornerB |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute||Unit of coordinate system for RoomCornerA and RoomCornerB |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |} ac30be2cdfca39e11cfc8a28f46d3fe7c6ed3f51 2446 2445 2022-05-30T12:06:16Z Isfmiho 3 wikitext text/x-wiki Spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||narrative description of the room |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute||Type of coordinate system for RoomCornerA and RoomCornerB |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute||Unit of coordinate system for RoomCornerA and RoomCornerB |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |} d562c190fa48a35b82757ff773311fc22f1d2d73 2 551 2448 2022-07-18T08:10:40Z Petibub 4 Creating user page for new user. wikitext text/x-wiki Prof. Yu received his BSc degree (2002) in Mechanical from Huazhong Agriculture University, and and PhD degree (2009) in Acoustic from South Chia University of Technology. From 2002 to 2004, he worked as an Electronic and Testing Engineer in Companies. Prof. Yu joined the Acoustic lab, School of Physics and Optoelectronics in July 2009 as a Lecture and was promoted to Associate Professor and later Professor of Acoustics. His recent research includes Electronic Acoustics, Architecture Acoustics, Psychoacoustics, Spatial Audio, Binaural Hearing and Sound Signal Processing. 70b23fd38c0dba04b3c54b8f801760dc3140f778 3 552 2449 2022-07-18T08:10:40Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 10:10, 18 July 2022 (CEST) 8aeeaa965b22e243d749a499db2b63c5dfe24c31 0 17 2453 2452 2022-07-18T12:08:29Z Petibub 4 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New: [http://sofacoustics.org/data/database/scut SCUT]''': Near-field HRTFs with anthropometric data (see CSV and PDF). ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. ac771d1e3999947d4d770e8b1010029c70e3d39a 2455 2453 2022-07-18T12:10:35Z Petibub 4 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New: [http://sofacoustics.org/data/database/scut SCUT]''': Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- und high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 9c4c4aeadbee5626e9bae7339bdee1d45df1efb6 2458 2455 2022-09-09T07:39:05Z Isfmiho 3 /* Directivities (sources and receivers) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New: [http://sofacoustics.org/data/database/scut SCUT]''': Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 607ee0d9a9f5917f12cb8fbe2bdcd5adb1873ad3 2459 2458 2022-10-10T13:09:12Z Isfmiho 3 /* Example & Test SOFA Files */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New: [http://sofacoustics.org/data/database/scut SCUT]''': Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] (deprecated) == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. cf72a508f55a69d3ddfcf20c62d360e6d6f887b2 2460 2459 2022-10-10T13:21:04Z Isfmiho 3 /* Example & Test SOFA Files */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New: [http://sofacoustics.org/data/database/scut SCUT]''': Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 9ce9e694b89348aefc73c857ea8c30ea4edfc9e6 0 1 2454 2451 2022-07-18T12:09:26Z Petibub 4 SCUT: HRTFs and anthropometric data wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 5c1759b779f97c3ae46f99c7ef8a1e197bf16373 2491 2454 2022-10-21T11:37:21Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox 2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 67a2d37463fe5d5fb6e6d9311205721be7eb5142 2492 2491 2022-10-21T11:37:46Z Isfmiho 3 /* News history */ wikitext text/x-wiki SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 280bd86718eaf13b2a8f5a915bc08560a1723d69 2493 2492 2022-10-21T11:42:14Z Isfmiho 3 wikitext text/x-wiki '''*** UPDATE *** ''' '''[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.''' SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 579e66353452f41ee729523c322fb023170fb60a 2494 2493 2022-10-21T11:44:47Z Isfmiho 3 wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 4df8e13efd38adc650928eb588da67b755b23cda 2495 2494 2022-10-21T11:48:51Z Isfmiho 3 /* UPDATE: SOFA Toolbox v2.1 has been released. See Software and APIs for details. */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 34cfa9974a40dc53de22e38ea2a20b33948110c3 2 553 2456 2022-07-25T12:50:47Z Petibub 4 Creating user page for new user. wikitext text/x-wiki Communication University of China，Recording Art of Grade 2019 (Recording Engineering) 5ea64037e8682e0881b78e20a02ad41647df9cb8 3 554 2457 2022-07-25T12:50:47Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 14:50, 25 July 2022 (CEST) 0a0469bd48a54f7adbc2e494ae16857a52dcb521 0 5 2461 2444 2022-10-18T08:16:27Z Isfmiho 3 /* Deprecated SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! f11240d71f75dbca215ee90ef916a17ef964148b 2473 2461 2022-10-21T10:18:11Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2020 (SOFA 2.0), we are currently working on: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! f6d04de8af1b993c4a4c991a44308eb1e138c4aa 2486 2473 2022-10-21T11:29:11Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2015 (SOFA 1.0), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. As with AES69-2022 (SOFA 2.1), we have: * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 5bc7d81c5f73601164f889fb015f512aca52d93b 2487 2486 2022-10-21T11:30:49Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we have: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 12dee0edd51ce114d4afb0266fd38eadb7ca30c6 2488 2487 2022-10-21T11:31:06Z Isfmiho 3 /* Standardized SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available There are currently no proposed conventions. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 051ae4e40e9aa8261217c6da7531b4702439fcb9 0 498 2462 2373 2022-10-21T10:05:37Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or '2-way loudspeaker' |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or 'LoudspeakerCompany' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, 'The bell'. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, 'Viewing direction of the bell'. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, 'Along the keys, keys up'. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki>{''}</nowiki>||||IS, MS||string||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki>{''}</nowiki>||||MS||string||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki>440</nowiki>||||I, M||double||Frequency (in hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded and will be called "FreeFieldDirectivityTF" from version 1.0 again (according to SOFA standard). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 1ac3e84666f54dc605792b38e5a42ae0276f2b09 2463 2462 2022-10-21T10:06:18Z Isfmiho 3 wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1. == This version uses SOFA 2.1 which reflects the AES69-2022 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.1</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or '2-way loudspeaker' |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or 'LoudspeakerCompany' |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., 'The bell' for a trumpet or 'On the front plate between the low- and mid/high-frequency unit' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., 'Viewing direction of the bell' for a trumpet or 'Perpendicular to the front plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., 'Along the keys, keys up' for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position. In a simple settings, a single emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||MS, ES, MES||string||A more detailed description of the Emitters. For example, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki>{''}</nowiki>||||MS||string||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki>440</nowiki>||||I, M||double||Frequency (in hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Units used for N |} == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or '2-way loudspeaker' |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or 'LoudspeakerCompany' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, 'The bell'. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, 'Viewing direction of the bell'. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, 'Along the keys, keys up'. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki>{''}</nowiki>||||IS, MS||string||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki>{''}</nowiki>||||MS||string||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki>440</nowiki>||||I, M||double||Frequency (in hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded and will be called "FreeFieldDirectivityTF" from version 1.0 again (according to SOFA standard). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} e278557b05233fae56e768e7a5a8128864079f31 2464 2463 2022-10-21T10:06:29Z Isfmiho 3 wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.1 == This version uses SOFA 2.1 which reflects the AES69-2022 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.1</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or '2-way loudspeaker' |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or 'LoudspeakerCompany' |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., 'The bell' for a trumpet or 'On the front plate between the low- and mid/high-frequency unit' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., 'Viewing direction of the bell' for a trumpet or 'Perpendicular to the front plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., 'Along the keys, keys up' for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position. In a simple settings, a single emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||MS, ES, MES||string||A more detailed description of the Emitters. For example, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki>{''}</nowiki>||||MS||string||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki>440</nowiki>||||I, M||double||Frequency (in hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Units used for N |} == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or '2-way loudspeaker' |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or 'LoudspeakerCompany' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, 'The bell'. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, 'Viewing direction of the bell'. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, 'Along the keys, keys up'. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki>{''}</nowiki>||||IS, MS||string||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki>{''}</nowiki>||||MS||string||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki>440</nowiki>||||I, M||double||Frequency (in hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded and will be called "FreeFieldDirectivityTF" from version 1.0 again (according to SOFA standard). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 77a0029a4bbca9ff3836fb9a810177813a237dfc 0 549 2465 2392 2022-10-21T10:08:14Z Isfmiho 3 wikitext text/x-wiki The convention is an extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter (instead of a source position), and a consistent measurement for a single listener and all directions is described by a set of the emitter positions (instead of source positions) surrounding the listener. The data type 'FIR-E' is used (instead of 'FIR' as in [[SimpleFreeFieldHRIR]]). The conventions is defined since AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldHRIR</nowiki>||rm||||attribute||An extension of SimpleFreeFieldHRIR in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Short name of the listener (as for example the subject ID). |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Source position is assumed to be the ListenerPosition in order to reflect Emitters surrounding the Listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Radius in 'spherical harmonics', Position in 'cartesian' and 'spherical' |- |EmitterPosition:Type||<nowiki>spherical harmonics</nowiki>||m||||attribute||Can be 'spherical harmonics', 'cartesian', or 'spherical' |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mrne||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRI, MRI, MRE||double||Additional delay of each IR (in samples) |} d7009d09587d65080a30cb1227f18b1f62244aec 2468 2465 2022-10-21T10:12:12Z Isfmiho 3 wikitext text/x-wiki The convention is an extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter (instead of a source position), and a consistent measurement for a single listener and all directions is described by a set of the emitter positions (instead of source positions) surrounding the listener. The data type 'FIR-E' is used (instead of 'FIR' as in [[SimpleFreeFieldHRIR]]). The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldHRIR</nowiki>||rm||||attribute||An extension of SimpleFreeFieldHRIR in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Short name of the listener (as for example the subject ID). |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Source position is assumed to be the ListenerPosition in order to reflect Emitters surrounding the Listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Radius in 'spherical harmonics', Position in 'cartesian' and 'spherical' |- |EmitterPosition:Type||<nowiki>spherical harmonics</nowiki>||m||||attribute||Can be 'spherical harmonics', 'cartesian', or 'spherical' |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mrne||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRI, MRI, MRE||double||Additional delay of each IR (in samples) |} aaa5adc1cc127ff7c094aadba940074a43ecfc98 0 538 2466 2437 2022-10-21T10:10:35Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldHRTF</nowiki>||rm||||attribute||This conventions is for HRTFs created under conditions where room information is irrelevant and stored as SH coefficients |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Source position is assumed to be the ListenerPosition in order to reflect Emitters surrounding the Listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Radius in 'spherical harmonics', Position in 'cartesian' and 'spherical' |- |EmitterPosition:Type||<nowiki>spherical harmonics</nowiki>||m||||attribute||Can be 'spherical harmonics', 'cartesian', or 'spherical' |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mrne||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRNE||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute|| |} b5dbaa33880f63e76238959ed1d952cffd9bcce2 0 534 2467 2370 2022-10-21T10:11:36Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with any datatype (no restrictions at all). The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>General</nowiki>||rm||||attribute||This conventions is for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||m||||attribute||The datatype can be arbitrary |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmiiterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |} f5b43024252a9d1065632fe9c10c218329b12438 0 286 2469 2385 2022-10-21T10:13:02Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki __TOC__ == Description == This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} == Version 0.9 == Version 0.9 is deprecated. Please use Conventions version 1.0 instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.9</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} c89212332c26c5cf2a4b5443bbb857895d327a19 2470 2469 2022-10-21T10:13:40Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki __TOC__ == Description == This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements == Version 1.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} == Version 0.9 == Version 0.9 is deprecated. Please use Conventions version 1.0 instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.9</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} 4dcb42f3fa67b6a9c80b9586f36432e9feed6212 2471 2470 2022-10-21T10:13:51Z Isfmiho 3 /* Description */ wikitext text/x-wiki __TOC__ == Description == This conventions defines only that FIR is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions. Examples: * the exact measurement setup of an HRTF set, * raw data of headphone measurements. == Version 1.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} == Version 0.9 == Version 0.9 is deprecated. Please use Conventions version 1.0 instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.9</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |} 6351ca31a285071dd83851bf816e0ea6925a730c 0 531 2472 2368 2022-10-21T10:15:31Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed [[GeneralFIR]] convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIR-E</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, EC, ECM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrne||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} f2a50ec78e3e0add94ce0c1d5c1d6ea38c904a93 0 550 2474 2364 2022-10-21T10:19:21Z Isfmiho 3 wikitext text/x-wiki Conventions for testing the string support. Version 0.2 included in SOFA 1.0. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralString</nowiki>||rm||||attribute||Conventions for testing the string support |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>String</nowiki>||rm||||attribute||We store strings here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |String2||<nowiki>{'' ''}</nowiki>||m||MRS||string|| |- |String2:Description||<nowiki>2-D string</nowiki>||m||||attribute|| |- |String2:Units||<nowiki>latin1</nowiki>||m||||attribute|| |- |Data.String1||<nowiki>{''}</nowiki>||m||MS||string|| |- |Data.String1:Description||<nowiki>1-D string</nowiki>||m||||attribute|| |- |Data.String1:Units||<nowiki>latin1</nowiki>||m||||attribute|| |- |Data.String2||<nowiki>{'' ''}</nowiki>||m||MRS||string|| |- |Data.String2:Description||<nowiki>2-D string</nowiki>||m||||attribute|| |- |Data.String2:Units||<nowiki>latin1</nowiki>||m||||attribute|| |- |Data.Double||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.Double:Units||<nowiki>double</nowiki>||m||||attribute|| |} ab3182d146f2f3faa64f29cb49ec6267ac2ae821 0 287 2475 2383 2022-10-21T11:22:25Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki __TOC__ ==Description== This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == Version 1.0 is deprecated. Please use Conventions version 2.0 instead. Name Default Flags Dimensions Type Comment GLOBAL:Conventions SOFA rm attribute GLOBAL:Version 1.0 rm attribute GLOBAL:SOFAConventions GeneralTF rm attribute This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. GLOBAL:SOFAConventionsVersion 1.0 rm attribute GLOBAL:APIName rm attribute GLOBAL:APIVersion rm attribute GLOBAL:ApplicationName attribute GLOBAL:ApplicationVersion attribute GLOBAL:AuthorContact m attribute GLOBAL:Comment m attribute GLOBAL:DataType TF rm attribute We store frequency-dependent data here GLOBAL:History attribute GLOBAL:License No license provided, ask the author for permission m attribute GLOBAL:Organization m attribute GLOBAL:References attribute GLOBAL:RoomType free field m attribute The room information can be arbitrary GLOBAL:Origin attribute GLOBAL:DateCreated m attribute GLOBAL:DateModified m attribute GLOBAL:Title m attribute ListenerPosition [0 0 0] m IC, MC double ListenerPosition:Type cartesian m attribute ListenerPosition:Units metre m attribute ReceiverPosition [0 0 0] m rCI, rCM double ReceiverPosition:Type cartesian m attribute ReceiverPosition:Units metre m attribute SourcePosition [0 0 1] m IC, MC double In order to store different directions/positions around the listener, SourcePosition is assumed to vary SourcePosition:Type spherical m attribute SourcePosition:Units degree, degree, metre m attribute EmitterPosition [0 0 0] m eCI, eCM double EmitterPosition:Type cartesian m attribute EmitterPosition:Units metre m attribute Data.Real 0 m mRn double The real part of the complex spectrum Data.Imag 0 m MRN double The imaginary part of the complex spectrum N 0 m N double Frequency values N:LongName frequency m attribute narrative name of N N:Units hertz m attribute Unit of the values given in N fe7d8c8ce66bdce1919040edc4c86a7356fb9dd0 2476 2475 2022-10-21T11:22:46Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki __TOC__ ==Description== This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == Version 1.0 is deprecated. Please use Conventions version 2.0 instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} f9dc8ba8d52788711598fde4f9293ba53e9b18f7 2477 2476 2022-10-21T11:23:01Z Isfmiho 3 /* Version 2.0 */ wikitext text/x-wiki __TOC__ ==Description== This conventions defines only that TF is the DataType. All other metadata follow the general SOFA specifications. This conventions can be used to save data which are too general to store in more specific conventions, e.g., exact configuration of sources and receivers in a BEM simulation. == Version 2.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>2.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 1.0 == Version 1.0 is deprecated. Please use Conventions version 2.0 instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF</nowiki>||rm||||attribute||This conventions stores TFs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralFIR. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} 02086a230384417c7ca9fbd0d3bc8d7e22e7cfe3 0 533 2478 2369 2022-10-21T11:23:23Z Isfmiho 3 wikitext text/x-wiki This conventions defines a general convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends [[GeneralTF]] by having Emitter as an explicit dimension in the data. The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralTF-E</nowiki>||rm||||attribute||This conventions stores TFs depending in the Emiiter for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined. This convention is based on GeneralTF |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute||We store frequency-dependent data depending on the emitter here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, EC, ECM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mrne||double||The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double||The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the values given in N |} b44a3ec0ed0ee155b56263cd0fa4c6998325cbab 0 9 2479 2367 2022-10-21T11:25:05Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.4, we use SourcePosition to represent the different HRTF directions. By doing so, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the last version before AES69-2015, we adapted the conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). SimpleFreeFieldHRIR version 1.0 represents the current standardized convention set from AES69-2015. == Version 1.0 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This convention set essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This convention set can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 H 0; 0 -H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRIR</nowiki>||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||||||attribute|| |} == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Version 0.4 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} afabef3ef86bfb5b18c1658306e9d821945c4c4a 0 532 2480 2372 2022-10-21T11:25:34Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is SOS. The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRSOS</nowiki>||rm||||attribute||This convention set follows SimpleFreeFieldHRIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0; 0 0 0 1 0 0], [3 1 2]);</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} 9e50c68f1a4a6ce7127a146a323ebeb77490c748 0 535 2481 2438 2022-10-21T11:26:08Z Isfmiho 3 wikitext text/x-wiki This conventions defines free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRIR]], the only difference is the DataType, that is TF. The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRTF</nowiki>||rm||||attribute||This conventions is for HRTFs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Real||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.Imag||<nowiki>[0 0]</nowiki>||m||MRN||double|| |- |N||<nowiki>0</nowiki>||m||N||double|| |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute|| |} 0fffe526bd8d3fed1eecf64ccea0ba6cf571eecb 0 459 2482 2376 2022-10-21T11:27:00Z Isfmiho 3 /* Version 1.0 */ wikitext text/x-wiki == Description == Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. [[File:SimpleHeadphoneIR-0.2.png|right|thumb|225px]] In conventions ''SimpleHeadphoneIR'' we store IRs of the system headphone-ear, i.e. headphone IRs. The most important properties of ''SimpleHeadphoneIR'' are: * '''One-to-one correspondence between emitters and receivers''': When measuring headphones, we usually have two headphones (=two emitters, E1 and E2) and we have two mics places in the ears (=two receivers, R1 and R2). In the first measurement we measure E1-->R1,R2; in the second one we measure: E2-->R1, R2. Usually, IRs E1-->R1 and E2-->R2 are the interesting IRs and are further processed. Note the correspondence of the emitter and receiver indices: This one-to-one correspondence of emitters and receivers is '''a strict property''' of ''SimpleHeadphoneIR''. (If you also need the crosstalk IRs, i.e., E1-->R2 and E2-->R1, ''GeneralFIR'' is recommended). * '''Single listener''': in a single file, IRs of a single listener are stored. Note that multiple measurements of the same listener can still be stored in a single file. Note the correspondence to ''SimpleFreeFieldHRIR'', in which the HRTFs are also restricted to those of a single listener. To this end: ** DatabaseName: represents the name of the database, ideally corresponding to an existing HRTF database ** ListenerShortName: represents the ID of the subject from the DatabaseName, ideally corresponding to the same subject on the corresponding HRTF database * '''Multiple measurements''' (of the single listener): multiple measurements are described as repeated measurements of the same listener. The repetition might have various reasons: ** No modifications at all, i.e., simple re-measuring the IRs. It that case, the measurement time/date has changed, which will be captured by MeasurementDate for each M. ** Position of the headphones change: It that case, the measurement time/date and the source/emitter position/orientation have changed, which will be captured by the corresponding variables for each M. ** The headphones might change, e.g. by measuring IRs of different headphones. In that case, the metadata describing the headphones are a function of M and are represented as string variables. Note that these metadata, when being not M-dependent are represented as mandatory global attributes. At the moment, we consider the following metadata as being potentially a function of M: *** SourceManufacturer: name of the headphones manufacturer (global attribute: mandatory; M-dependent variable: optional) *** SourceModel: name of the headphone model. Must uniquely describe the headphones of a manufacturer (global attribute: mandatory; M-dependent variable: optional). *** SourceURI: URI to the specs of the headphones (global attribute: mandatory; M-dependent variable: optional). *** ReceiverDescription: stores narrative information about the microphones (global attribute: mandatory; M-dependent variable: optional). *** EmitterDescription: stores narrative information about the headphones emitter (global attribute: mandatory; M-dependent variable: optional). == Version 1.0 == This version uses SOFA 2.1 which reflects the AES69-2022 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescriptions||<nowiki>{''}</nowiki>||||MS||string||R-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||MS||string||E-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Old, deprecated versions == For historical reasons the older versions of the SimpleHeadphoneIR (or HeadphoneIR) Convention are listed below. === Version 0.2 === This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} === Version 0.1, previously proposed as HeadphoneIR (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleHeadphoneIR||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||0.1||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute||We will store IRs here |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute||Room type is not relevant here |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 0]||m||IC, MC||double||Headphones are located at the position of the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 -0.09 0; 0 0.09 0]||m||eCI, eCM||double||Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||to which HRTF database these data correspond? |- |GLOBAL:SubjectID||||m||||attribute||to which subject from the database these data correspond? |- |GLOBAL:SourceProducer||||||||attribute||who produced the headphones? |- |GLOBAL:SourceModel||||||||attribute||how is this headphone called? |- |GLOBAL:ProcessingState||||||||attribute||how are the IRs processed (raw, equalized, etc)? |- |GLOBAL:ListenerDescription||||||||attribute||describe the listener here (human, dummy head, etc) |- |GLOBAL:SourceDescription||||||||attribute||describe the headphones here |- |GLOBAL:ReceiverDescription||||||||attribute||describe the microphones here |- |GLOBAL:EmitterDescription||||||||attribute||describe the drivers of the headphones here |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleHeadphoneIR</nowiki>||rm||||attribute||Conventions for IRs with a 1-to-1 correspondence between emitter and receiver. The main application for this convention is to store headphone IRs recorded for each emitter and each ear. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||We will store IRs here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||Room type is not relevant here |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Default: Headphones are located at the position of the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||eCI, eCM||double||Default: Reflects the correspondence of each emitter to each receiver |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Correspondence to a database |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||Correspondence to a subject from the database |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the listener (or mannequin) |- |GLOBAL:SourceDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphones |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Name of the headphones manufacturer |- |SourceManufacturer||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceManufucturer |- |GLOBAL:SourceModel||<nowiki></nowiki>||m||||attribute||Name of the headphone model. Must uniquely describe the headphones of the manufacturer |- |SourceModel||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute SourceModel |- |GLOBAL:SourceURI||<nowiki></nowiki>||m||||attribute||URI of the headphone specifications |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the microphones |- |ReceiverDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute ReceiverDescription |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||m||||attribute||Narrative description of the headphone drivers |- |EmitterDescription||<nowiki>{''}</nowiki>||||MS||string||Optional M-dependent version of the attribute EmitterDescription |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} 27e8981588c417e1d63868a9fd2c44c29dc4443d 0 537 2483 2435 2022-10-21T11:27:58Z Isfmiho 3 wikitext text/x-wiki This conventions defines SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomMIMOSRIR</nowiki>||rm||||attribute||Single-room multiple-input multiple-output spatial room impulse responses, depending on Emitters |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute||Shall be FIR-E |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:RoomShortName||<nowiki></nowiki>||||||attribute||Short name of the Room |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||Informal verbal description of the room |- |GLOBAL:RoomLocation||<nowiki></nowiki>||||||attribute||Location of the room |- |GLOBAL:RoomGeometry||<nowiki></nowiki>||||||attribute||URI to a file describing the room geometry. |- |RoomTemperature||<nowiki>0</nowiki>||||I, M||double||Temperature during measurements, given in Kelvin. |- |RoomTemperature:Units||<nowiki>kelvin</nowiki>||||||attribute||Units of the room temperature |- |RoomVolume||<nowiki>0</nowiki>||||I, MI||double||Volume of the room |- |RoomVolume:Units||<nowiki>cubic metre</nowiki>||||||attribute||Units of the room volume |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverDescriptions||<nowiki>{''}</nowiki>||||RS, RSM||string||R-dependent version of the attribute ReceiverDescription |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||ES, ESM||string||E-dependent version of the attribute EmitterDescription |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, ECI, ECM||double||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrne||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRI, MRI, MRE||double||Additional delay of each IR (in samples) |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement. |} dea2797b9ba2b8a1f3fe7fffdb60640e1e7bd8da 0 536 2484 2446 2022-10-21T11:28:34Z Isfmiho 3 wikitext text/x-wiki Spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. The conventions is defined in AES69-2020 (SOFA 2.0). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:RoomShortName||<nowiki></nowiki>||||||attribute||Short name of the Room |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||Informal verbal description of the room |- |GLOBAL:RoomLocation||<nowiki></nowiki>||||||attribute||Location of the room |- |GLOBAL:RoomGeometry||<nowiki></nowiki>||||||attribute||URI to a file describing the room geometry. |- |RoomTemperature||<nowiki>0</nowiki>||||I, M||double||Temperature during measurements, given in Kelvin. |- |RoomTemperature:Units||<nowiki>kelvin</nowiki>||||||attribute||Units of the room temperature. |- |RoomVolume||<nowiki>0</nowiki>||||I, M||double||Volume of the room. |- |RoomVolume:Units||<nowiki>cubic metre</nowiki>||||||attribute||Units of the room volume. |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverDescriptions||<nowiki>{''}</nowiki>||||RS, RSM||string||R-dependent version of the attribute ReceiverDescription |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||ES, ESM||string||E-dependent version of the attribute EmitterDescription |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} f9978515476b40c967a06daf084f9704ab3faf25 2485 2484 2022-10-21T11:28:43Z Isfmiho 3 wikitext text/x-wiki Spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:RoomShortName||<nowiki></nowiki>||||||attribute||Short name of the Room |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||Informal verbal description of the room |- |GLOBAL:RoomLocation||<nowiki></nowiki>||||||attribute||Location of the room |- |GLOBAL:RoomGeometry||<nowiki></nowiki>||||||attribute||URI to a file describing the room geometry. |- |RoomTemperature||<nowiki>0</nowiki>||||I, M||double||Temperature during measurements, given in Kelvin. |- |RoomTemperature:Units||<nowiki>kelvin</nowiki>||||||attribute||Units of the room temperature. |- |RoomVolume||<nowiki>0</nowiki>||||I, M||double||Volume of the room. |- |RoomVolume:Units||<nowiki>cubic metre</nowiki>||||||attribute||Units of the room volume. |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverDescriptions||<nowiki>{''}</nowiki>||||RS, RSM||string||R-dependent version of the attribute ReceiverDescription |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||ES, ESM||string||E-dependent version of the attribute EmitterDescription |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} ec23ad79fbd9cec4c4b2dd241ed1ee33198bccf3 0 555 2489 2022-10-21T11:32:32Z Isfmiho 3 Created page with "__TOC__ == Description == This conventions follows [[GeneralFIR]] but the data is stored as second-order section (SOS) coefficients. == Version 1.0 == {| border="1" !Name !De..." wikitext text/x-wiki __TOC__ == Description == This conventions follows [[GeneralFIR]] but the data is stored as second-order section (SOS) coefficients. == Version 1.0 == {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralSOS</nowiki>||rm||||attribute||This conventions follows GeneralFIR but the data is stored as second-order section (SOS) coefficients. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>SOS</nowiki>||rm||||attribute||Filters described as second-order section (SOS) coefficients |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||In order to store different directions/positions around the listener, SourcePosition is assumed to vary |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0], [3 1 2]);</nowiki>||m||mrn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Broadband delay (in samples resulting from SamplingRate) |} 612a5178589c5943466cad516f77faea97f59828 0 15 2490 2442 2022-10-21T11:35:46Z Isfmiho 3 wikitext text/x-wiki == HDFView: Generic SOFA file viewer == SOFA files are based on [http://en.wikipedia.org/wiki/NetCDF netCDF-4]. NetCDF is based on [http://en.wikipedia.org/wiki/Hdf5 HDF5]. [http://www.hdfgroup.org/hdf-java-html/hdfview/ HDFView] is a generic viewer for [http://en.wikipedia.org/wiki/Hdf5 HDF5] files running in Java. Thus, SOFA files can be loaded and edited in the HDFView. This is a generic viewer; it allows browsing through all metadata and data in a numeric format only. == SOFA Toolbox for Matlab/Octave (previously SOFA API Matlab/Octave) == SOFA Toolbox for Matlab/Octave aims at providing a basic interface for handling SOFA files in Matlab and Octave. The releases are provided at [https://sourceforge.net/projects/sofacoustics/ Sourceforge]. The sources are stored at [https://github.com/sofacoustics/sofa github] == SOFA API for C++ == An API for C++ is available online. The version 1.0 is in accordance with the AES69-2015 standard. The sources are stored at [https://github.com/sofacoustics/API_Cpp github]. If you have questions about this API, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the list moderator. == pysofaconventions: SOFA API for Python == [https://github.com/andresperezlopez/pysofaconventions pysofaconventions] is a SOFA API for Python made by Andrés Pérez-López (UPF/Eurecat, Spain). It is a full implementation of SOFA including reading and writing SOFA files, taking the C++ API as a reference. It supports automatic installation via [https://pypi.org/project/pysofaconventions/ the pip system]. == pySOFA: Lightweight SOFA API for Python (read-only, FIR only) == [https://github.com/Jencke/pySOFA pySOFA] is a SOFA API for Python made by Jörg Encke (TUM, Munich). The API is currently read-only and implements the FIR Datatype. It was implemented for a specific project and only implements a limited amount of features. If you have question about this API, feel free to contact [https://github.com/Jencke Jörg Encke] or to submit [https://github.com/Jencke/pySOFA/issues an issue report]. == SOFASonix: Lightweight SOFA API for Python (read/write support, all conventions) == [https://github.com/OneBadNinja/SOFASonix SOFASonix] is another lightweight SOFA API for Python made by Ioseb Laghidze (ISVR, Southampton University, UK). It supports both reading and writing of SOFA files for the conventions defined at the time of writing. The API is a full implementation of SOFA with built-in validation-checks for compliance with each convention and a generator of convention templates for quickly creating SOFA files. SOFASonix runs on an SQLite database, making it backwards compatible with previous versions of each convention. == sofar: Maybe the most complete Python package for the SOFA file format (read/write support) == [https://pypi.org/project/sofar/ sofar] is a SOFA API for Python made by Fabian Brinkmann. It supports both reading and writing of SOFA files. The API allows adding custom data & attributes to SOFA files and verifying its content with respect to the data type and shape. == libmysofa: Lightweight SOFA API in C (reading) == [https://github.com/hoene/libmysofa Libmysofa] is a light weight C-library intended to read SOFA files for spatial rendering. It hardly has any library dependencies and is suitable for embedded devices. It can read SOFA files and check whether the data comply the "SimpleFreeFieldHRIR" conventions. In addition, provides functions to look-up and interpolate the filters for a given orientation and to normalize the HRTFs to a reference level. It compiles unter Linux (CMake) and Windows (Visual Studio 2015). == WebSofa: SOFA API in JavaScript == [https://github.com/CWBudde/WebSofa WebSofa] is slightly based on the libmysofa research for loading HDF files without much dependencies. However, in contrast to the low level c library this library is meant to be executed in a JavaScript environment (such as any modern browser or [https://nodejs.org/en/ Node.js]). So far it is not completed as it's just a hobby project, but it already allows to display properties of a given SOFA file. Try it out in the [https://rawgit.com/CWBudde/WebSofa/master/Demo/www/index.html online demo]. == sofa~: SOFA for [https://cycling74.com Max] == [https://github.com/APL-Huddersfield/SOFA-for-Max SOFA for Max] is a collection of objects made by Dale Johnson and Hyunkook Lee ([https://www.hud.ac.uk/apl/resources University of Huddersfield], UK) for using and creating SOFA files in [https://cycling74.com Max]. It is based on libsofa C++ API and enables SOFA files to be utilized in patches designed for spatial audio reproduction. The binaries are available for [ https://doi.org/10.5281/zenodo.3269271 MacOS and Windows]. == Application: IRCAM Spat == [https://forum.ircam.fr/projects/detail/spat/ Spat] is a software suite for sound spatialisation in real-time in music creation, post-production, and live performances. It supports SOFA for binaural rendering. == Application: IRCAM Panoramix == [https://forum.ircam.fr/projects/detail/panoramix/ Panoramix] is a standalone application for spatial audio mixing and post-production. It supports SOFA for binaural rendering. == Application: SOFAlizer plug-in for VLC player == SOFAlizer is a simple demo of an audio engine as a plugin for the [http://www.videolan.org/vlc/ VLC-Player]. Currently, Windows binaries of the VLC-Player 2.1 compiled with the SOFAlizer plugin are available. Details on the installation can be found [https://github.com/sofacoustics/SOFAlizer/releases/tag/0.1.0 here]. The source code is available [https://github.com/sofacoustics/SOFAlizer here]. The file [https://github.com/sofacoustics/SOFAlizer/blob/master/modules/audio_filter/sofalizer/sofalizer.c sofalizer.c] can serve as an example of how to load SOFA files in C++. == Application: DirPat == [https://opendata.iem.at/projects/dirpat/ DirPat] is a set of tools aiming at the analysis and visualization of the directivity of acoustic sources like loudspeakers, microphones, singers, talkers, and music instruments. DirPat consists of user interfaces, signal-processing tools, and a database of measured directivities which are handled as SOFA files. == Application: 3D Tune-In Toolkit == [https://github.com/3DTune-In/3dti_AudioToolkit 3D Tune-In Toolkit] is a standard C++ library for audio spatialization via headphones. It was developed within the [http://www.3d-tune-in.eu 3D Tune-In project] aiming at using 3D sound and simulating hearing loss and hearing aids within virtual environments and games. == Application: Anaglyph VST == [http://anaglyph.dalembert.upmc.fr Anaglyph VST] is a [https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugins VST effect plugin] for binaural rendering with SOFA files in a digital-audio workstation. Anaglyph includes a personalizable morphological ITD model, near-field ILD corrections, and HRTF parallax selection, among other features. == Application: Binaural Audio == The [https://kutt.it/binaural Binaural Audio project] aims to introduce people to binaural audio. It provides audio samples (including HRTF and SOFA files) within its large [https://airtable.com/shrHEOlBTzftrnVKY/tbloLjoZKWJDnLtTc database]. == Application: Webcam Headtracker == The [https://github.com/eac-ufsm/webcam-headtracker Webcam Headtracker Application] by the Federal University of Santa Maria (Brazil) and the ISVR in Southampton is software-based, which means you don't need any special hardware attached to your head, only a webcam video feed, so the model can infer the listener's head orientation and positioning, making it a handy approach to many applications involving spatialized audio. == Application: Individualized HRTF App == The [https://github.com/davircarvalho/Individualized_HRTF_Synthesis/tree/master/Individualized%20HRTF%20App Individualized HRTF App] by the Federal University of Santa Maria (Brazil) is a MATLAB-based app capable of generating HRTFs in SOFA and [https://sourceforge.net/p/hesuvi/wiki/Help/ HeSuVi] WAV formats by providing [https://i.imgur.com/AwnMMyb.png personal measurements of head and ears]. More info about the Individualized HRTF Synthesis project can be found on [https://github.com/davircarvalho/Individualized_HRTF_Synthesis Github]. 22a16223d2ce4a9cb1b09727492fc22343d53604 0 16 2496 2349 2022-10-21T11:51:23Z Isfmiho 3 wikitext text/x-wiki * '''[https://www.oeaw.ac.at/en/ari/our-team/majdak-piotr Piotr Majdak]''' ([https://www.oeaw.ac.at/en/ari/ Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): project leader, Matlab support * '''[https://www.noisternig.com/ Markus Noisternig]''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): specifications, standardization * '''[https://www.qu.tu-berlin.de/menue/team/alumni/hagen_wierstorf/ Hagen Wierstorf]''' ([https://www.qu.tu-berlin.de/menue/qu/ Quality and Usability Lab], [http://www.tu-berlin.de/ Technical University of Berlin]): Octave support * '''[https://www.oeaw.ac.at/en/ari/our-team/mihocic-michael Michael Mihocic]''' ([https://www.oeaw.ac.at/en/ari/ Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): Website support, Matlab support * '''Harald Ziegelwanger''' ([https://www.oeaw.ac.at/en/ari/ Acoustics Research Institute], [http://www.oeaw.ac.at/ Austrian Academy of Sciences]): specifications * '''Thibaut Carpentier''' ([http://www.ircam.fr/ UMR STMS IRCAM-CNRS-UPMC]): C++ API, specifications SOFA was initiated in January 2012 during the 4th AABBA meeting in Berlin (Blauert, 2009). Since then, many other researches helped by providing feedback and support: * '''Matthieu Parmentier''' ([http://www.francetelevisions.fr/ France Television]): initiation of the [http://www.aes.org/ AES] standardization * '''Wolfgang Hrauda''' ([http://iem.at Institute for Electronic Music and Acoustics], [http://www.kug.ac.at University of Arts and Music], Graz) * '''Bruce Olson, AESSC Chair''': [http://www.aes.org/ AES] standardization committee chair * '''Mark Yonge, AESSC Secretary''': [http://www.aes.org/ AES] standardization committee secretary * '''Rozenn Nicol''' ([http://laborange.fr/ Orange Labs, France Telecom]) * '''[http://steinhardt.nyu.edu/faculty_bios/view/Agnieszka_Roginska Agnieszka Roginska]''' ([http://steinhardt.nyu.edu/ Music Technology, New York University]) * '''[http://www.ais.riec.tohoku.ac.jp/Member/yoh/ Yôiti Suzuki]''' ([http://www.riec.tohoku.ac.jp/index-e.shtml Research Institute of Electrical Communication, Tohoku University]) * '''Kanji Watanabe''' ([http://www.akita-pu.ac.jp/language/EN/ Faculty of Engineering, Akita Prefectural University]) * '''Yukio Iwaya''' (Faculty of Engineering, Tohoku Gakuin University) * '''Michele Geronazzo''' (University of Padova): headphone support Also many thanks go to the '''[http://www.aes.org/ AES] standardization team''' for their support. == Contact == If you have questions about SOFA, please send an email to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You need to be a member of the mailing list to send a message to the list. You don't need to be a member to send an email to the moderator. Also you are invited to contact the standardization committee of X212. Join us at [http://www.aes.org/standards/development/membership.cfm] and select "SC-02-08-E" from the list. == References == Blauert, J., Braasch, J., Bucholz, J., Colburn, H.S., Jekosch, U., Kohlrausch, A., Mourjopoulos, J., Pulkki, V., Raake, A. (2009) "Aural assessment by means of binaural algorithms - The AABBA project" in proceedings of the International Symposium on Auditory and Audiological Research (ISSAR), Helsingør, Denmark. d9e4eca2c1cfb4bc92b1e121ca536fd341da5fe5 0 11 2497 2300 2022-10-21T11:55:32Z Isfmiho 3 /* SOFA 2.0 */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.0 === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2 === Datatypes standardized in SOFA 2.0 and SOFA 2.1: ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} f12345939efe22c9a8a4f370dfc5bd8b96aa9a12 2498 2497 2022-10-21T11:55:49Z Isfmiho 3 /* Data Types */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are '''preliminary''' and are not finalized yet! The draft is under revision, open for comments and available on [https://www.aes.org/standards/comments/cfc-draft-rev-aes69-xxxx-201206.cfm aes.org] Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.x === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.x === Datatypes standardized in SOFA 2.0 and SOFA 2.1: ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} 8f7e0af44269214aaeeaefe82951d965c7e81787 2499 2498 2022-10-21T11:57:05Z Isfmiho 3 /* Specifications */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. A document with SOFA 1.0 specs is under preparation. SOFA 2.0 specifications are defined in the the reaffirmed standards [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.x === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.x === Datatypes standardized in SOFA 2.0 and SOFA 2.1: ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} aa54e65519c43bcab72613a522a34dadb025c74d 2500 2499 2022-10-21T11:57:24Z Isfmiho 3 /* Specifications */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. SOFA 2.0 specifications are defined in the the reaffirmed standards [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.x === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.x === Datatypes standardized in SOFA 2.0 and SOFA 2.1: ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} 10c98a818c1b33465e1b43e774b31bc7ea877c76 2501 2500 2022-10-21T11:59:05Z Isfmiho 3 /* Specifications */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. SOFA 2.x specifications are defined in the the reaffirmed standards [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.x === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.x === Datatypes standardized in SOFA 2.0 and SOFA 2.1: ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} 3c4e21dd2acbeae853f6ddd84f7ecc7cd074297b 0 478 2502 2386 2022-11-21T08:38:31Z Isfmiho 3 /* Description */ wikitext text/x-wiki ==Description== This SOFA convention set is similar to [[GeneralFIR]]. The only difference is the DataType, which is FIR'''E''', not FIR. All other attributes and variables follow the general SOFA specifications. As GeneralFIR, this convention set can be used to save data which are too general to store in more specific conventions. GeneralFIRE is deprecated; [[GeneralFIR-E]] is recommended instead. == Version 1.0 == This version follows the conventions [[GeneralFIR]] (version 1.0) standardized in AES69-2015. Note that GeneralFIRE 1.0, in contrast to GeneralFIR 1.0, has not been included in the standard, thus, here, we declare it as stable. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} == Old deprecated versions == === Version 0.1 === {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>0.6</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>GeneralFIRE</nowiki>||rm||||attribute||This conventions stores IRs for general purposes, i.e., only the mandatory, SOFA general metadata are pre-defined |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute||We use FIR datatype which in addition depends on Emitters (E) |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, meter</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double||Each speaker is represented as an emitter. Use EmitterPosition to represent the position of a particular speaker. Size of EmitterPosition determines E |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>meter</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[1 1]</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IRE, MRE||double||Additional delay of each IR (in samples) |} f2bebcef6369a73abf08530f55c15b015e5f10ee 0 17 2503 2460 2022-12-02T10:34:43Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio. Each set of HRTFs contains 451 directions (91 loudspeakers, five manual roations of the subjects), see McLachlan et al. (2022) (under review). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New: [http://sofacoustics.org/data/database/scut SCUT]''': Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 2c09a87ec425918bf929cee0bc0b04bda998808f 2505 2503 2022-12-02T10:39:37Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see McLachlan et al. (2022) (under review). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New: [http://sofacoustics.org/data/database/scut SCUT]''': Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. b9a5e6ffc29409c32bb8990f54ddac97b79cd32f 2506 2505 2022-12-02T13:42:36Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * '''New: [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]''': In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see McLachlan et al. (2022) (under review). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * '''New: [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]''': Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. fb4993b2152672284daba52dad31a080e08ec3ac 2507 2506 2022-12-02T13:43:00Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * '''New: [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]''': In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see McLachlan et al. (2022) (under review). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *'''New: [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]''': SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]''': SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 84a31dba8c1dea1fa17b37b987ef15618b1b00c5 2508 2507 2023-02-08T09:16:18Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * '''New: [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]''': In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see McLachlan et al. (2022) (under review). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/dechorate/ dEchorate dataset]''': Multichannel room impulse responses (RIRs) with annotations of early echo timings and 3D positions of microphones and sources under different wall configurations in a cuboid room. For description, see [https://asmp-eurasipjournals.springeropen.com/articles/10.1186/s13636-021-00229-0 here] ''(Credit: Diego Di Carlo, Rennes)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * '''ARI free-field HRTF database'''. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * '''Example files''' created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. fefb65da8ea1f8a94eb07e0a2162bc0f5e4f4c22 2509 2508 2023-02-08T09:16:45Z Isfmiho 3 /* Other repositories */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * '''New: [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]''': In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see McLachlan et al. (2022) (under review). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. *'''New: [https://sofacoustics.org/data/database/dechorate/ dEchorate dataset]''': Multichannel room impulse responses (RIRs) with annotations of early echo timings and 3D positions of microphones and sources under different wall configurations in a cuboid room. For description, see [https://asmp-eurasipjournals.springeropen.com/articles/10.1186/s13636-021-00229-0 here] ''(Credit: Diego Di Carlo, Rennes)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 5bebdd0567a39879b7b9e164ea693bd11799811d 2511 2509 2023-02-08T09:21:29Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * '''New: [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]''': In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see McLachlan et al. (2022) (under review). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 1c9654c1fdbe467de1a921fc2a5dbf6e3d45de11 2534 2511 2023-06-06T15:05:43Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * '''New: [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]''': In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see McLachlan et al. (2022) (under review). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 69523d948d66de2e818b4e5fe4a0668cf836d20e 2535 2534 2023-06-21T09:58:18Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 8da2b9b16fd4a827cdf0e7a7930ad044c0192b71 2538 2535 2023-07-03T11:29:59Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New: [http://sofacoustics.org/data/database/axd AXD]''': HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 5af970b5302cf54dfe7360bf5a85ef8f668cbf61 2539 2538 2023-07-03T11:30:24Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New:''' [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. f71aae2d2113fbd8cd328e01b7a2247418e680d7 2540 2539 2023-07-03T11:30:42Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New:''' [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. d6a4bc10aac8a2fb375b88ba0dbd20ed9cf33e8c 2542 2540 2023-07-03T11:46:01Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New:''' [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New:''' [http://sofacoustics.org/data/database/axd%20(kemar) AXD Kemar]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. d16edb12edad17eb72196525a095fc7cebb4c8d9 2543 2542 2023-07-03T11:46:42Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New:''' [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New:''' [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. *[https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. *[https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 7272e8215782339a7b278138aaeb23695d1e76ac 0 1 2504 2495 2022-12-02T10:36:50Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released b7c5ad73525a86fe260d472e1907e70bee9b6388 2510 2504 2023-02-08T09:17:53Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 08.02.2023: dEchorate database added (Credit: Diego Di Carlo, Rennes). * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 74b67ce9234f1e672d531dd206efe635b4b4bfed 2512 2510 2023-02-08T09:21:59Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released b7c5ad73525a86fe260d472e1907e70bee9b6388 2541 2512 2023-07-03T11:31:40Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 03.07.2023: AXD HRTFs from the SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released b9c219aba8e401bb89e3a3ef7cb3eebdc04b469a 2544 2541 2023-07-03T11:47:53Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 83c0a0ddc5632e08b47dcc3150af4d51c6db23b6 2552 2544 2023-07-11T08:23:28Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released ca699490663f86ec74c66d15c1b0fc0d6763d985 2 556 2513 2023-02-17T18:22:48Z Petibub 4 Creating user page for new user. wikitext text/x-wiki A Video&Audio programmer. Write video player ( support iOS/Android/Windows/Mac; support HDR/Space Audio). 627ade97caaaf17c0d0fe3b7b9ba991d0b12d4ed 3 557 2514 2023-02-17T18:22:49Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 19:22, 17 February 2023 (CET) 32538bd62ca6a4e2d1a10aa713a24a5e3da89a31 2 558 2515 2023-03-21T08:53:11Z Petibub 4 Creating user page for new user. wikitext text/x-wiki Hi Michael! I'm just testing the account registration feature. 0e2afc56d84c584830f785182c3c6a7b013be899 3 559 2516 2023-03-21T08:53:11Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 09:53, 21 March 2023 (CET) f9b0cff8f9d4b1a9572cb81bd1776effcb419648 2 560 2517 2023-03-24T14:14:40Z Jw 959 Creating user page for new user. wikitext text/x-wiki asdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdf 1776c8c074b01a41a10596b5d4124fcd63469574 3 561 2518 2023-03-24T14:14:40Z Jw 959 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Jw|Jw]] ([[User talk:Jw|talk]]) 15:14, 24 March 2023 (CET) d6ccb4d0d30f1cb7c8d720257f294f4508193200 2 562 2519 2023-03-24T14:23:51Z Jw 959 Creating user page for new user. wikitext text/x-wiki asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf 7bed4a4944a10d17b8e06cd244bdad69a71e07c9 3 563 2520 2023-03-24T14:23:51Z Jw 959 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Jw|Jw]] ([[User talk:Jw|talk]]) 15:23, 24 March 2023 (CET) 6c9df01405f3350514ca136945dae3972b0714b4 2 564 2521 2023-03-24T14:37:38Z Jw 959 Creating user page for new user. wikitext text/x-wiki asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf 016e8467c3f8f7882c246c53053ec05f0a0f5b7c 3 565 2522 2023-03-24T14:37:38Z Jw 959 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Jw|Jw]] ([[User talk:Jw|talk]]) 15:37, 24 March 2023 (CET) 8d2a44080379912b79a3e5feb3c682bdb0c93e4e 2 566 2523 2023-03-27T06:08:12Z Jw 959 Creating user page for new user. wikitext text/x-wiki asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf 016e8467c3f8f7882c246c53053ec05f0a0f5b7c 3 567 2524 2023-03-27T06:08:12Z Jw 959 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Jw|Jw]] ([[User talk:Jw|talk]]) 08:08, 27 March 2023 (CEST) 97ac76a004a9bcb6f64806583635a431c2732e03 2 568 2525 2023-03-27T06:27:42Z Jw 959 Creating user page for new user. wikitext text/x-wiki bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla 2a778421e38cb499bfd9752f7ffb033cc2332838 3 569 2526 2023-03-27T06:27:42Z Jw 959 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Jw|Jw]] ([[User talk:Jw|talk]]) 08:27, 27 March 2023 (CEST) a8b6acab26750db9ecfd775723ff8cfc4113fda1 2 570 2527 2023-03-27T07:16:42Z Jw 959 Creating user page for new user. wikitext text/x-wiki bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla 2a778421e38cb499bfd9752f7ffb033cc2332838 3 571 2528 2023-03-27T07:16:42Z Jw 959 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Jw|Jw]] ([[User talk:Jw|talk]]) 09:16, 27 March 2023 (CEST) 747a9ba1f353f730bf51fcbb08feed3e50bf1334 0 5 2529 2488 2023-05-09T11:22:42Z Isfmiho 3 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available Currently available proposed conventions: * [[SingleTrackedAudio]]: Conventions for recording audio. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 25387e30168f33424ec62dbe117fcf0efca136bc 2532 2529 2023-05-09T11:26:25Z Isfmiho 3 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available Currently available proposed conventions: * [[SingleTrackedAudio]]: Conventions to record audio data annotated with geometric information. . == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! ec436e19bbc4ade5374d4f03b31cae2b07ba3c69 2533 2532 2023-05-09T11:26:43Z Isfmiho 3 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available Currently available proposed conventions: * [[SingleTrackedAudio]]: Conventions to record audio data annotated with geometric information. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 036f8668a26b0616b851ab79587c4b730bcd2265 2545 2533 2023-07-07T07:16:39Z Isfmiho 3 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available Currently available proposed conventions: * [[AnnotatedReceiverAudio]]: Conventions to store (binaural) audio data at the receivers, annotated with geometric information. * [[AnnotatedEmitterAudio]]: Conventions to store audio data at the ermitters, annotated with geometric information. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 92a22e57a11ad5296a9a4c78e74796caa0933417 2546 2545 2023-07-07T07:16:50Z Isfmiho 3 /* Deprecated SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available Currently available proposed conventions: * [[AnnotatedReceiverAudio]]: Conventions to store (binaural) audio data at the receivers, annotated with geometric information. * [[AnnotatedEmitterAudio]]: Conventions to store audio data at the ermitters, annotated with geometric information. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. * [[SingleTrackedAudio]]: Conventions to record audio data annotated with geometric information. Deprecated: Please use [[AnnotatedReceiverAudio]] or [[AnnotatedEmitterAudio]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 5cadbebac434be9f5b069e37f9e5788b47390489 0 572 2530 2023-05-09T11:23:03Z Isfmiho 3 Created page with "{| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleTrackedAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |..." wikitext text/x-wiki {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleTrackedAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the head. IC if not tracked, MC if tracked. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||IC, RC, RCM||double||Position of the ears. RC if not tracked, RCM if tracked. |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the virtual ensemble. IC if not tracked, MC if tracked. |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position of the virtual source(s). eC if not tracked, eCM if tracked. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Must be of the same dimensionality as ListenerView. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the head. IC if not tracked, MC if tracked. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |M||<nowiki>0</nowiki>||m||m||double||Time stamp of the measurements in M,defines the size of M. |- |EmitterUp||<nowiki>[0 0 0]</nowiki>||||EC, ECM||double||Must be of the same dimensionality as EmitterView. |- |EmitterView||<nowiki>[0 0 0]</nowiki>||||EC, ECM||double||Orientation of the virtual source(s). EC if not tracked, ECM if tracked. |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.Sample||<nowiki>[0 0]</nowiki>||m||rn||double||n=number of audio samples |- |Data.SamplingRate||<nowiki>44100</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |M:LongName||<nowiki>time</nowiki>||m||||attribute||Narrative name for M |- |M:Units||<nowiki>second</nowiki>||m||||attribute||Units used for M |} b7585c284902be318a8f8079d7d543a358d5e5ad 2531 2530 2023-05-09T11:26:00Z Isfmiho 3 wikitext text/x-wiki Conventions to record audio data annotated with geometric information. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleTrackedAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the head. IC if not tracked, MC if tracked. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||IC, RC, RCM||double||Position of the ears. RC if not tracked, RCM if tracked. |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the virtual ensemble. IC if not tracked, MC if tracked. |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position of the virtual source(s). eC if not tracked, eCM if tracked. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Must be of the same dimensionality as ListenerView. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the head. IC if not tracked, MC if tracked. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |M||<nowiki>0</nowiki>||m||m||double||Time stamp of the measurements in M,defines the size of M. |- |EmitterUp||<nowiki>[0 0 0]</nowiki>||||EC, ECM||double||Must be of the same dimensionality as EmitterView. |- |EmitterView||<nowiki>[0 0 0]</nowiki>||||EC, ECM||double||Orientation of the virtual source(s). EC if not tracked, ECM if tracked. |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.Sample||<nowiki>[0 0]</nowiki>||m||rn||double||n=number of audio samples |- |Data.SamplingRate||<nowiki>44100</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |M:LongName||<nowiki>time</nowiki>||m||||attribute||Narrative name for M |- |M:Units||<nowiki>second</nowiki>||m||||attribute||Units used for M |} e0fd53349b1d463a9e6a3244c05b34707379eb76 2547 2531 2023-07-07T07:17:37Z Isfmiho 3 wikitext text/x-wiki Conventions to record audio data annotated with geometric information. Deprecated: Please use [[AnnotatedReceiverAudio]] or [[AnnotatedEmitterAudio]] instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleTrackedAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the head. IC if not tracked, MC if tracked. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||IC, RC, RCM||double||Position of the ears. RC if not tracked, RCM if tracked. |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the virtual ensemble. IC if not tracked, MC if tracked. |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position of the virtual source(s). eC if not tracked, eCM if tracked. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Must be of the same dimensionality as ListenerView. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the head. IC if not tracked, MC if tracked. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |M||<nowiki>0</nowiki>||m||m||double||Time stamp of the measurements in M,defines the size of M. |- |EmitterUp||<nowiki>[0 0 0]</nowiki>||||EC, ECM||double||Must be of the same dimensionality as EmitterView. |- |EmitterView||<nowiki>[0 0 0]</nowiki>||||EC, ECM||double||Orientation of the virtual source(s). EC if not tracked, ECM if tracked. |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.Sample||<nowiki>[0 0]</nowiki>||m||rn||double||n=number of audio samples |- |Data.SamplingRate||<nowiki>44100</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |M:LongName||<nowiki>time</nowiki>||m||||attribute||Narrative name for M |- |M:Units||<nowiki>second</nowiki>||m||||attribute||Units used for M |} 605c3c4379d9c3ad12811da2dff1f31e119addbe 0 11 2536 2501 2023-06-23T12:52:23Z Isfmiho 3 /* SOFA 2.x */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. SOFA 2.x specifications are defined in the the reaffirmed standards [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.x === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.x === Datatypes standardized in SOFA 2.0 and SOFA 2.1: ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} cf796f5ac816eaebad6e593ce46b04f279ad7bbf 2537 2536 2023-06-23T12:53:30Z Isfmiho 3 /* SOFA 2.x */ wikitext text/x-wiki == Specifications == * SOFA 1.0 is reflected by the [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] standard. It mostly corresponds to SOFA 0.6, which specs can be downloaded [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.6.pdf/download here]. SOFA 2.x specifications are defined in the the reaffirmed standards [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. Older specs: * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.5.pdf/download Version 0.5: Download specifications] * [[Proposal 0.4 | Version 0.4: Discussion on the specifications]] (closed) * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.3.pdf/download Version 0.3: Download specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.2.pdf/download Version 0.2: Specifications] * [http://sourceforge.net/projects/sofacoustics/files/SOFA%20specs%200.1%20%28as%20of%20AES%202013%29.pdf/download Version 0.1: Specifications as presented at the AES Convention 2013 in Rom] == Coordinate system == SOFA 1.0 supports two coordinates systems: [https://en.wikipedia.org/wiki/Cartesian_coordinate_system Cartesian] and spherical in the azimuth/elevation representation. [[file:Coordinate_system.png]] SOFA 2.0 adds a spatially ''continuous'' representation of receivers by means of the coordinate type 'spherical harmonics'. To this end, data depending on the position of the receivers are stored as real-valued spherical harmonic coefficients along the dimension R. Thus, each subset of data for a specific R corresponds not to a specific receiver position, but to a specific spherical harmonic order and degree. Along the dimension R , the data are stored in the [https://en.wikipedia.org/wiki/Ambisonic_data_exchange_formats#ACN ACN order]. The spatially continuous representation is indicated by the ReceiverPosition_Type of 'Spherical Harmonics', ReceiverPosition_Units is 'metre', and the ReceiverPosition stores the information about the radius only. SOFA 2.0 further adds the spatially continuous representation of emitters, which uses the same scheme as that of receivers. == Data Types == === SOFA 1.x === ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== FIRE (deprecated) ==== FIRE is the proposed version of FIR-E. With FIR-E being standardized, we strongly discourage from using it, use [https://www.sofaconventions.org/mediawiki/index.php/SOFA_specifications#FIR-E FIR-E] instead. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIRE</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} === SOFA 2.x === Datatypes standardized in SOFA 2.0 and SOFA 2.1: ==== FIR ==== For storing impulse responses. Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mRn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== FIR-E ==== FIR-E is based on FIR and is intended for storing impulse responses which depend on the emitter (E). Note: Delay is mandatory (set to 0 if not used). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>FIR-E</nowiki>||rm||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mREn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the samples in Data.IR |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IRE, MRE||double||Additional delay of each IR (always in samples, i.e. units of N) |} ==== TF ==== Useful to describe a transfer function by a sparse number of frequencies. The guys from BEM simulations like it. Note: the dimensional variable N is mandatory, it must be of dimension N, and must provide the frequency values. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== TF-E ==== TF-E is based on TF and is intended for storing impulse responses which depend on the emitter (E). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:DataType||<nowiki>TF-E</nowiki>||rm||||attribute|| |- |Data.Real||<nowiki>0</nowiki>||m||mRnE||double|| The real part of the complex spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRNE||double|| The imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double|| Frequency values |- |N_LongName||<nowiki>frequency</nowiki>||||||attribute|| |- |N_Units||<nowiki>hertz</nowiki>||m||||attribute|| Unit of the values given in N |} ==== SOS ==== This DataType stores a filter as a broadband delay and an arbitrary number of second order sections (SOSs). The transfer function H(z) of a filter can be described as: <math>H(z) = \frac{B_1(z)}{A_1(z)} \cdot \frac{B_2(z)}{A_2(z)} \cdot ... \cdot \frac{B_p(z)}{A_p(z)}</math> where <math>p</math> is the number of second order sections, <math>A(z)</math> is denominator representing the poles of a filter, and <math>B(z)</math> is numerator representing the zeros of a filter. Then, each SOS can be described as: <math>B_i(z) = b_{i,0} + b_{i,1} z^{-1} + b_{i,2} z^{-2}</math> <math>A_i(z) = a_{i,0} + a_{i,1} z^{-1} + a_{i,2} z^{-2}</math> Note that usually, <math>A_i(z)</math> is normalized such that <math>a_{i,0} = 1</math>. Thus, in the DataType SOS, a filter is represented by three mandatory variables: * Data.SamplingRate: sampling rate used to describe the filter. * Data.Delay: broadband delay (in samples resulting from SamplingRate). Note: Use Delay of zero when not used.used). * Data.SOS: list of coefficients of all SOSs. ** Size: Data.SOS has the size of '''[ M R N ]''' with N as the total number of coefficients, thus an integer multiple of 6 corresponding to <math>6p</math>. ** Format of the list: Along the dimension N, the list goes like: <math>[ b_{1,0}\ b_{1,1}\ b_{1,2}\ a_{1,0}\ a_{1,1}\ a_{1,2}\ b_{2,0}\ b_{2,1}\ b_{2,2}\ a_{2,0}\ a_{2,1}\ a_{2,2}\ ... b_{p,0}\ b_{p,1}\ b_{p,2}\ a_{p,0}\ a{p,1}\ a_{p,2} ]</math> which corresponds to <math>[ B_1(z)\ A_1(z)\ B_2(z)\ A_2(z)\ ... B_p(z)\ A_p(z) ]</math> {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |Data.SOS||<nowiki>permute([0 0 0 1 0 0],[3 1 2])</nowiki>||m||mRn||double||Filter coefficients as SOS coefficients. |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I||double||Sampling rate of the coefficients in Data.SOS and the delay in Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||MR||double||Broadband delay (in samples resulting from SamplingRate) |} 2441d7c53388a7a2c6df5cea9737a90f8aca1dac 0 573 2548 2023-07-07T07:19:10Z Isfmiho 3 Created page with "Conventions to record and store (binaural) audio data at the receivers, annotated with geometric information. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>AnnotatedReceiverAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFACo..." wikitext text/x-wiki Conventions to record and store (binaural) audio data at the receivers, annotated with geometric information. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>AnnotatedReceiverAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>Audio</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the head. IC if not tracked, MC if tracked. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rC, rCM||double||Position of the ears. RC if not tracked, RCM if tracked. |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the virtual ensemble. IC if not tracked, MC if tracked. |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position of the virtual source(s). eC if not tracked, eCM if tracked. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Must be of the same dimensionality as ListenerView. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the head. IC if not tracked, MC if tracked. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Receiver||<nowiki>[0 0]</nowiki>||m||nI, nR||double||(binaural) audio data at the receivers; n=number of audio samples |- |Data.SamplingRate||<nowiki>44100</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |M||<nowiki>0</nowiki>||m||m||double||Time stamp of the measurements in M, defines the size of M. |- |M:LongName||<nowiki>time</nowiki>||m||||attribute||Narrative name for M |- |M:Units||<nowiki>second</nowiki>||m||||attribute||Units used for M |- |Response||<nowiki></nowiki>||||I, C, S||attribute||the subject’s response |- |Response:Type||<nowiki></nowiki>||||I, C, S||attribute||type depends on the dimension |- |Response:LongName||<nowiki></nowiki>||||S||attribute||narrative description of the response type |} 7acb8db71f84fceb9a376a4005249ff7aacf9522 2551 2548 2023-07-10T12:31:12Z Isfmiho 3 wikitext text/x-wiki Conventions to record and store (binaural) audio data at the receivers, annotated with geometric information. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>AnnotatedReceiverAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>Audio</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the head. IC if not tracked, MC if tracked. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rC, rCM||double||Position of the ears. RC if not tracked, RCM if tracked. |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the virtual ensemble. IC if not tracked, MC if tracked. |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position of the virtual source(s). eC if not tracked, eCM if tracked. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Must be of the same dimensionality as ListenerView. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the head. IC if not tracked, MC if tracked. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Receiver||<nowiki>[0 0]</nowiki>||m||In, Rn||double||(binaural) audio data at the receivers; n=number of audio samples |- |Data.SamplingRate||<nowiki>44100</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |M||<nowiki>0</nowiki>||m||m||double||Time stamp of the measurements in M, defines the size of M. |- |M:LongName||<nowiki>time</nowiki>||m||||attribute||Narrative name for M |- |M:Units||<nowiki>second</nowiki>||m||||attribute||Units used for M |- |Response||<nowiki></nowiki>||||I, C, S||attribute||the subject’s response |- |Response:Type||<nowiki></nowiki>||||I, C, S||attribute||type depends on the dimension |- |Response:LongName||<nowiki></nowiki>||||S||attribute||narrative description of the response type |} a9b4c4f854b228573b8643955550a30d3bb8756d 0 574 2549 2023-07-07T07:19:12Z Isfmiho 3 Created page with "Conventions to record and store audio data at the emitters, annotated with geometric information. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>AnnotatedEmitterAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVers..." wikitext text/x-wiki Conventions to record and store audio data at the emitters, annotated with geometric information. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>AnnotatedEmitterAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>Audio</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the head. IC if not tracked, MC if tracked. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rC, rCM||double||Position of the ears. RC if not tracked, RCM if tracked. |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the virtual ensemble. IC if not tracked, MC if tracked. |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position of the virtual source(s). eC if not tracked, eCM if tracked. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Must be of the same dimensionality as ListenerView. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the head. IC if not tracked, MC if tracked. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Emitter||<nowiki>[0 0]</nowiki>||m||nI, nE||double||audio data at the emitter(s); n=number of audio samples |- |Data.SamplingRate||<nowiki>44100</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |M||<nowiki>0</nowiki>||m||m||double||Time stamp of the measurements in M, defines the size of M. |- |M:LongName||<nowiki>time</nowiki>||m||||attribute||Narrative name for M |- |M:Units||<nowiki>second</nowiki>||m||||attribute||Units used for M |- |Response||<nowiki></nowiki>||||I, C, S||attribute||the subject’s response |- |Response:Type||<nowiki></nowiki>||||I, C, S||attribute||type depends on the dimension |- |Response:LongName||<nowiki></nowiki>||||S||attribute||narrative description of the response type |} 840a10d827bbf1a1702311b19824faac1ef7c7cb 2550 2549 2023-07-10T12:30:54Z Isfmiho 3 wikitext text/x-wiki Conventions to record and store audio data at the emitters, annotated with geometric information. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>AnnotatedEmitterAudio</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>Audio</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the head. IC if not tracked, MC if tracked. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rC, rCM||double||Position of the ears. RC if not tracked, RCM if tracked. |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position of the virtual ensemble. IC if not tracked, MC if tracked. |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position of the virtual source(s). eC if not tracked, eCM if tracked. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Must be of the same dimensionality as ListenerView. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the head. IC if not tracked, MC if tracked. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.Emitter||<nowiki>[0 0]</nowiki>||m||In, En||double||audio data at the emitter(s); n=number of audio samples |- |Data.SamplingRate||<nowiki>44100</nowiki>||m||I||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |M||<nowiki>0</nowiki>||m||m||double||Time stamp of the measurements in M, defines the size of M. |- |M:LongName||<nowiki>time</nowiki>||m||||attribute||Narrative name for M |- |M:Units||<nowiki>second</nowiki>||m||||attribute||Units used for M |- |Response||<nowiki></nowiki>||||I, C, S||attribute||the subject’s response |- |Response:Type||<nowiki></nowiki>||||I, C, S||attribute||type depends on the dimension |- |Response:LongName||<nowiki></nowiki>||||S||attribute||narrative description of the response type |} 9fd8b91843dbcb605ae014fa9974d4a7f54d0252 0 5 2553 2546 2023-08-10T08:20:57Z Isfmiho 3 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available Currently available proposed conventions: * [[AnnotatedEmitterAudio]]: Conventions to store audio data at the ermitters, annotated with geometric information. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. * [[SingleTrackedAudio]]: Conventions to record audio data annotated with geometric information. Deprecated: Please use [[AnnotatedReceiverAudio]] or [[AnnotatedEmitterAudio]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! b10a76933a09614f7d04660acf8950b3e3e0fa3d 2554 2553 2023-08-10T08:21:09Z Isfmiho 3 /* Stable SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available and can be read/modified by at least one publicly available software package. * [[GeneralString]]: Conventions for testing the string support. * [[AnnotatedReceiverAudio]]: Conventions to store (binaural) audio data at the receivers, annotated with geometric information. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available Currently available proposed conventions: * [[AnnotatedEmitterAudio]]: Conventions to store audio data at the ermitters, annotated with geometric information. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. * [[SingleTrackedAudio]]: Conventions to record audio data annotated with geometric information. Deprecated: Please use [[AnnotatedReceiverAudio]] or [[AnnotatedEmitterAudio]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 3ea1aacc05965cb0f418c14af9dbcc0d9177344b 2566 2554 2023-09-12T18:01:30Z Petibub 4 /* Stable SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available, have been checked by the SOFA team for consistency, and can be read/modified by at least one publicly available software package. They have version of 1.0 at least. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. If you would like to propose a new convention, consider the following rules: * Data must exist (do not foresee the future) * Data can not be described by existing SOFA conventions * Relevant information about the data available Currently available proposed conventions: * [[AnnotatedEmitterAudio]]: Conventions to store audio data at the ermitters, annotated with geometric information. == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. * [[SingleTrackedAudio]]: Conventions to record audio data annotated with geometric information. Deprecated: Please use [[AnnotatedReceiverAudio]] or [[AnnotatedEmitterAudio]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 88eb89362b6d593fabc8b5bd7b0bdced723d2dd3 2567 2566 2023-09-12T18:02:56Z Petibub 4 /* Proposed SOFA conventions */ wikitext text/x-wiki SOFA conventions specify the description of data and metadata for a particular kind of measured data. This is important in order to meet the different requirements coming from different application fields, specified. For example, description of HRTFs, BRIRs, and DRIRs requires different metadata. Also, some applications may prefer to see the data stored in a different way. These conventions, once approved by the peer group are defined in SOFA conventions. Specification of conventions are displayed in tables using the following legend: * '''Name''': the name of the metadata ** A colon: the metadata is an attribute *** "GLOBAL:": the metadata is a global attribute *** "X:Y": the metadata is an attribute Y of the variable X ** No colon: the metadata is a variable ** Data.X: the metadata is structured within the data * '''Default''': default value for the metadata ** An asterisk (*): special handling required, mentioned in the column Comment * <div id="AnchorFlags">'''Flags''':</div> ** r: read-only, must be the default value ** m: mandatory, must be saved in the file * <div id="AnchorDimensions">'''Dimensions''': dimensions of the metadata ** lower case: the variable size in that dimension determines the dimension size in the file ** upper case: variable must be of that dimension (or one of these dimensions) : Expand the following table to see the dimensions used in SOFA. Depending on the conventions there might be further restrictions. See [[SOFA specifications]] for more explanations. : {| class="mw-collapsible mw-collapsed wikitable" !Dimension !Description !Restrictions |- |M |number of measurements |integer >0 |- |R |number of receivers or harmonic coefficients describing receivers |integer >0 |- |E |number of emitters or harmonic coefficients describing emitters |integer >0 |- |N |number of data samples describing one measurement |integer >0 |- |S |number of characters in a string |integer ≥0 |- |style="color:gray" |I |style="color:gray" |singleton dimension, constant |style="color:gray" |always 1 |- |style="color:gray" |C |style="color:gray" |coordinate triplet, constant |style="color:gray" |always 3 |} == Standardized SOFA conventions == Standardized SOFA conventions are those which have been standardized by the AES. As with AES69-2022 (SOFA 2.1), we standardized the following conventions: * [[GeneralFIR]]: General convention with FIR as DataType (no restrictions but DataType) * [[GeneralTF]]: General convention with TF as DataType (no restrictions but DataType) * [[SimpleFreeFieldHRIR]]: Free-field HRTFs stored as impulse responses, measured with an omnidirectional source for a single listener. * [[GeneralFIR-E]]: General convention with FIR-E as DataType (no restrictions but DataType). GeneralFIR-E is the standardized version of the previously proposed GeneralFIR convention. It extends GeneralFIR by having Emitter as an explicit dimension in the data. * [[GeneralTF-E]]: General convention with TF-E as DataType (no restrictions but DataType). GeneralTF-E extends GeneralTF by having Emitter as an explicit dimension in the data. * [[GeneralSOS]]: General convention following [[GeneralFIR]] with SOS as DataType. * [[General]]: General convention with any datatype (no restrictions at all). * [[SimpleFreeFieldHRTF]]: Free-field HRTFs stored as transfer functions, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is TF. * [[SimpleFreeFieldHRSOS]]: Free-field HRTFs stored as second-order sections, measured with an omnidirectional source for a single listener. Based on SimpleFreeFieldHRIR, the only difference is the DataType, that is SOS. * [[FreeFieldHRTF]]: Free-field HRTFs stored as transfer functions in the spherical-harmonics domain, measured with an omnidirectional source for a single listener. Based on [[SimpleFreeFieldHRTF]], the only difference is that the HRTFs are in a spatially continuous representation. * [[FreeFieldHRIR]]: An extension of [[SimpleFreeFieldHRIR]] in order to consider more complex data sets described in spatially continuous representation. Each HRTF direction corresponds to an emitter, and a consistent measurement for a single listener and all directions is described by a set of the emitter positions surrounding the listener. * [[FreeFieldDirectivityTF]]: Convention for storing directivities of musical instruments or loudspeakers at spatial discrete points in the frequency domain. FreeFieldDirectivityTF is the standardized version of the previously proposed (Simple)FreeFieldDirectivityTF and MusicalInstrumentDirectivityTF. * [[SingleRoomSRIR]]: spatial room impulse responses (SRIRs) measured with an arbitrary number of receivers (R>1, such as a microphone array) and an omnidirectional source (E=1) in a single room. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. * [[SingleRoomMIMOSRIR]]: SRIRs measured with a compact listener containing an arbitrary number of receivers (R>1, such as a compact microphone array) and a compact source containing an arbitrary number of emitters (E>1, such as a multi-emitter loudspeaker) for multiple positions and/or orientations of the listener and/or source, in a single room. * [[SimpleHeadphoneIR]]: Conventions to store headphone IRs recorded for each emitter and each ear, single listener and no directionality of emitter/receiver considered. Note: Any modification in one of these conventions changes its status to "stable", i.e., not standardized anymore, unless the modification will be approved the AES. ==Stable SOFA conventions== Stable SOFA conventions are those for which SOFA files are publicly available, have been checked by the SOFA team for consistency, and can be read/modified by at least one publicly available software package. They have version of 1.0 at least. These conventions, when used often and widely, can be proposed for standardization to the AES. ==Proposed SOFA conventions== Proposed SOFA conventions are those being currently discussed and considered as work in progress. They have a version 0.x. Currently available proposed conventions: * [[GeneralString]]: Conventions for testing the string support. * [[AnnotatedReceiverAudio]]: Conventions to store (binaural) audio data at the receivers, annotated with geometric information. * [[AnnotatedEmitterAudio]]: Conventions to store audio data at the ermitters, annotated with geometric information. If you would like to propose a new convention, consider the following rules: * Data must exist or are being developed * Data can not be described by existing SOFA conventions * Relevant information about the data available == Ideas for future conventions == Here we list the suggestions and feedback from the peer group: * Include anthropometric data * Crosstalk cancellation filters * Include calibration data from the measurement * Include room pictures Please use the "Discussion" function to discuss these topics. ==Deprecated SOFA conventions== These conventions are deprecated because their proposal has changed or they have been standardized under different name. They are listed here for the sake of completeness only. When reading a SOFA file with a deprecated convention, convert to that stated below: * [[MusicalInstrumentDirectivityTF]]: use [[FreeFieldDirectivityTF]] instead. * SimpleFreeFieldDirectivityTF: use [[FreeFieldDirectivityTF]] instead. * [[SimpleBRIR]]: use [[SingleRoomSRIR]] instead. * [[GeneralFIRE]]: use [[GeneralFIR-E]] instead. * [[SimpleFreeFieldTF]]: use [[SimpleFreeFieldHRTF]] instead. * [[SimpleFreeFieldSOS]]: use [[SimpleFreeFieldHRSOS]] instead. * [[SingleRoomDRIR]]: use [[SingleRoomSRIR]] instead. * [[MultiSpeakerBRIR]]: use [[SingleRoomMIMOSRIR]] instead. * [[SingleTrackedAudio]]: Conventions to record audio data annotated with geometric information. Deprecated: Please use [[AnnotatedReceiverAudio]] or [[AnnotatedEmitterAudio]] instead. We strongly discourage from saving data with those conventions. == Feedback and Contribution == If you would like to contribute or propose new SOFA conventions: * Send an e-mail to the [mailto:sofacoustics-devel@lists.sourceforge.net mailing list]. You don't have to be a member of the mailing list to send a message to the moderator. * Go to one of the SOFA pages of your interest and use the "Discussion" for your contribution. We appreciate your feedback! 6c70604a15177dcde7bab907246d39278f4408fb 0 17 2555 2543 2023-08-29T13:13:27Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New:''' [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New:''' [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem%206drir-dl/ KAIST-IEM 6DRIR-DL dataset]: 6 DoF Directional Room Impulse Response Dataset Measured over a Dense Loudspeaker Grid (6DRIR-DL). For description, see [https://zenodo.org/record/8038733 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. e17f7d8d3fca41b0721a38e56d4c341772010beb 2556 2555 2023-08-29T13:13:56Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New:''' [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New:''' [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * '''New:''' [https://sofacoustics.org/data/database/kaist-iem%206drir-dl/ KAIST-IEM 6DRIR-DL dataset]: 6 DoF Directional Room Impulse Response Dataset Measured over a Dense Loudspeaker Grid (6DRIR-DL). For description, see [https://zenodo.org/record/8038733 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 4c6a0051bc879b264906b95379ff33761a9a0d65 2557 2556 2023-08-29T13:17:27Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New:''' [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New:''' [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * '''New:''' [https://sofacoustics.org/data/database/kaist-iem%206drir-dl/ KAIST-IEM 6DRIR-DL dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [https://zenodo.org/record/8038733 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 1a7e97f9b902f53281967739abae21a1e3183843 2558 2557 2023-08-30T06:00:11Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * '''New:''' [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * '''New:''' [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * '''New:''' [https://sofacoustics.org/data/database/kaist-iem%206drir-dl/ KAIST dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 3e227235cc563393e70a45885b0a1f6307d55f9c 2559 2558 2023-08-30T06:00:46Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * '''New:''' [https://sofacoustics.org/data/database/kaist-iem%206drir-dl/ KAIST dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 59cd02a51a08ca2c896e76cf412647fc58764509 2562 2559 2023-08-31T07:50:04Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * '''New:''' [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 54419be7c8c4dd09cead62f528eedd78971a1df1 2565 2562 2023-09-01T07:32:36Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" and "c" differ each other only in their starting positions and the order of measurement positions: b: 0°→0°, c: 270°→270°; direction always clockwise ↻) * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * '''New:''' [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. c5829abd4a39e01f3aa616be6446609be74af39e 2571 2565 2024-05-13T12:52:29Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; direction always clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * '''New:''' [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 0aa28cca9e86fbd42a91818325334a59ad2585f2 2572 2571 2024-05-21T11:13:50Z Isfmiho 3 wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; direction always clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Jacob Cooper, New York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 85eb3a0e84d8f6bf13a5ed08f4a4891d758820bc 2574 2572 2024-05-23T10:55:02Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c, dtf b/c: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; direction always clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 14272974aa59b365d05ca63ec54828a5a5c303d7 2575 2574 2024-06-25T08:32:50Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; direction always clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. e1a4c274a34e8c28775e3de2c1cfeb2c6defd339 2576 2575 2024-06-25T08:34:02Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject rotating clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 255424abf65946553bcc5fbec7f8b8e0715f77e3 2577 2576 2024-06-25T08:34:22Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 4b6653ce4c327bfb575ab5ee3203a7eda32e6fc5 2579 2577 2024-06-27T06:43:06Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == Standard (in-the-ear canal) HRTFs of humans: * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' HRTFs of artificial heads: * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from five dummy heads, measured at 2 distances. ''(Credit: Adrien Vidal, Bologna)'' Special HRTFs: * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. PRTFs: * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 74674874a233d50523667293e3b391aec2b6b9a5 2581 2579 2024-06-27T06:47:01Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans:=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads:=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from five dummy heads, measured at 2 distances. ''(Credit: Adrien Vidal, Bologna)'' ===Special HRTFs:=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs:=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == '''Sources''': * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' '''Receivers''': * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 086045cbc1f9256afd7273849fc0a872539cc53e 2582 2581 2024-06-27T06:47:28Z Isfmiho 3 /* Directivities (sources and receivers) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans:=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads:=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from five dummy heads, measured at 2 distances. ''(Credit: Adrien Vidal, Bologna)'' ===Special HRTFs:=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs:=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources:=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers:=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 8fef7065bcc39f4669959d11044e8d0d62354e18 2583 2582 2024-06-27T06:51:10Z Isfmiho 3 /* HRTFs of artificial heads: */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans:=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads:=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from five dummy heads, measured at 2 distances. Details can be found in the [https://hal.science/hal-03521905/document HAL publication]. ''(Credit: Adrien Vidal, Bologna)'' ===Special HRTFs:=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs:=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources:=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers:=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 51b8849bf55d0ef46f900416c03d7833f8dafb14 2584 2583 2024-06-27T08:57:06Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources:=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers:=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 509c5176129fdfdfeff62e43cc8ed9a10098cec8 2585 2584 2024-06-27T08:57:20Z Isfmiho 3 /* Directivities (sources and receivers) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 931255baafaadc8909894e40d25c6cb5406dae8a 2586 2585 2024-06-27T08:58:51Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. b6579ac5dea8c2fac00d3be39618ba923181e8fe 2587 2586 2024-07-05T10:07:48Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial Room Impulse Response Dataset: A Robot's Journey Through Coupled Rooms of a Reverberant University Building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)''. ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 6297bc5663e58171825a58356920c1c7db761a8c 2588 2587 2024-07-05T10:08:53Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial Room Impulse Response Dataset: A Robot's Journey Through Coupled Rooms of a Reverberant University Building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 7ebbe2932cbb4dadb0c69929d9fc3909b45682e2 2589 2588 2024-07-05T10:09:58Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * '''New:''' [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 931255baafaadc8909894e40d25c6cb5406dae8a 2590 2589 2024-07-05T10:10:31Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial Room Impulse Response Dataset: A Robot's Journey Through Coupled Rooms of a Reverberant University Building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 46f3f38abc87552ec919cb209f6ee2abb1d5b9b9 2592 2590 2024-07-05T10:13:05Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. d2a659b90e9fa2f6170dd2d6171b14936dc20874 2593 2592 2024-07-05T10:23:13Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 587cf2d9c2d3dacec3b1c17cdb9b4b726b6e96ff 2594 2593 2024-08-05T05:49:10Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * Tba: [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. ''(Credit: Giorgio Presti and Davide Fantini, University of Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 50c9d78e10704bc55e020f3182b3bbca6ee334cd 2595 2594 2024-08-05T05:49:35Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * Tba: [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. cf4d6a011260df28efda2c14a86291bab66b3782 2596 2595 2024-08-08T05:44:09Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kajni Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * Tba: [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 387bbf79a044a37ddfa6314d250840303e163e2c 2597 2596 2024-08-20T09:54:45Z Petibub 4 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * Tba: [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. f92b0ec32659183df36f540e18c04c482b709f90 2598 2597 2024-09-03T06:54:19Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. d6a6eef326ddd2b2f20f6a8b2438aeac6f485cac 2599 2598 2024-09-03T06:54:32Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each set of HRTFs contains 451 sound-source directions (91 loudspeakers by 5 subject roations), see [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]. * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 7fa1da60cbd57a42ad45be2caad5a3da91b35a50 2602 2599 2024-11-12T09:13:59Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]; but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 8aee9507f63081a31d7c97b60d3c55c67e22200d 0 1 2560 2552 2023-08-30T06:01:54Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 03.07.2023: KAIST: DRIRs from the KAIST database added (Credit: Jung-Woo Choi, KAIST, Korea) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released e9023be2949148a23ba8c0cd03661da26a4e933b 2561 2560 2023-08-30T06:02:12Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 29.08.2023: KAIST: DRIRs from the KAIST database added (Credit: Jung-Woo Choi, KAIST, Korea) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 9e700dcf036af3013e92bafa4cd9f39244c4b73c 2563 2561 2023-08-31T07:50:23Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 4a82fb702d12a79fd69c76ce5142ae8a0745d9f3 2564 2563 2023-09-01T07:32:23Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released e9321e31af1330707952b051aba0196740a732cd 2573 2564 2024-05-21T11:15:42Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===''' UPDATE: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.'''=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released ea573bd485126cb8ea05bd1965a3dbeeb1be91df 2578 2573 2024-06-27T06:40:48Z Isfmiho 3 /* UPDATE: SOFA Toolbox v2.1 has been released. See Software and APIs for details. */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 95c9350e30cfc87529f2413442027bb88cdb1883 2580 2578 2024-06-27T06:45:31Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Bologna) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 3449129427b8f160a209aa22632acf34f1a08d65 2591 2580 2024-07-05T10:12:23Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset for different acoustic room configurations added (Credit: Stephan Werner, Ilmenau) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset of a robot's journey through coupled rooms added (Credit: Stephan Werner, Ilmenau) * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Marseille) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 7ecff91fff173072304fbff70386b9f2ad2dda52 2600 2591 2024-09-03T06:56:14Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 03.09.2024: PAN-AR: SRIR dataset for different room and configurations added (Credit: Giorgio Presti and Davide Fantini, Milan) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset for different acoustic room configurations added (Credit: Stephan Werner, Ilmenau) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset of a robot's journey through coupled rooms added (Credit: Stephan Werner, Ilmenau) * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Marseille) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 71ef7407aef840d6e8f8aa4177c8af3249dfb51b 0 9 2568 2479 2024-04-02T16:49:50Z Petibub 4 /* Version 1.0 */ wikitext text/x-wiki ==Description== This conventions essentially defines the setup used to measure HRTFs in free field. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. We defined this conventions to describe data from databases like [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and others. In SimpleFreeFieldHRIR version 0.2, we used ListenerRotation to describe the different measurement directions, and the source was assumed to be in the center of the measurement setup. This, however, limited the use of SimpleFreeFieldHRIR, thus, in version 0.4, we use SourcePosition to represent the different HRTF directions. By doing so, more complex data can be described where the tilt of the head is varied, or the listener is not exactly in the center of the measurement setup. In SimpleFreeFieldHRIR version 0.4, the last version before AES69-2015, we adapted the conventions to SOFA 0.6. The most striking changes are: * ''Source'' has been renamed to '''Origin''' (in order to reduce the confusion with the object source) * ''SubjectID'' has been renamed to '''ListenerShortName''' (in order to be more consistent with the general naming of the metadata). SimpleFreeFieldHRIR version 1.0 represents the current standardized convention set from AES69-2015. == Version 1.0 == [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This convention set essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is usually two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This convention set can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Per default, two Receivers (=ears) are defined on a head with radius H (in meter, default: 0.09), thus, ReceiverPosition=[0 H 0; 0 -H 0]. Note that any positive integer number of Receivers can be used, though. * Source: Source consists of a single Emitter only. Per default, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. Per default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldHRIR</nowiki>||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0.09 0; 0 -0.09 0]</nowiki>||m||rCI, rCM||double|| |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||m||||attribute||ID of the subject from the database |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |Data.IR||<nowiki>[0 0]</nowiki>||m||mRn||double|| |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double|| |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute|| |- |Data.Delay||<nowiki>[0 0]</nowiki>||m||IR, MR||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||||IC, MC||double|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||||||attribute|| |} == Old, deprecated versions == For historical reasons the older versions of the SimpleFreeFieldHRIR Convention are listed below. === Version 0.4 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp and SourceView are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.6||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This convention set is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.4||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||||||attribute|| |- |GLOBAL:ApplicationVersion||||||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Origin||||||||attribute|| |- |GLOBAL:DateCreated||||m||||attribute|| |- |GLOBAL:DateModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:ListenerShortName||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |ListenerView:Type||cartesian||m||||attribute|| |- |ListenerView:Units||meter||m||||attribute|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Proposed for version 0.3 (deprecated) === [[File:SimpleFreeFieldHRIR-0.3.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Note that usually, only the apparent azimuth and elevation angles are provided and this information is modeled as the variation of the source position. This conventions can, however, also be used to describe more complex data where the tilt of the head is varied or the listener is not exactly in the center of the measurement setup. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Listener: The listener is in the origin of the setup, facing in the direction of the y-axis. Thus, for default values, ListenerPosition=[0 0 0], ListenerView=[1 0 0], ListenerUp=[0 0 1], all given in cartesian coordinates. * Receivers: Two receivers (=ears) on a head with radius H (in meter, default: 0.09): ReceiverPosition=[0 -H 0; 0 +H 0]. * Source: Source consists of a single emitter. For default values, EmitterPosition=[0 0 0] in cartesian coordinates. SourcePosition (in spherical coordinates!) varies corresponding to the different azimuth and elevation angles of the measurement directions. For default, SourcePosition=[0 0 1] (azimuth 0°, elevation 0°, distance 1 m). SourceUp, SourceView, and SourceRotation are not considered and optional. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||SOFA||rm||||attribute|| |- |GLOBAL:Version||0.5||rm||||attribute|| |- |GLOBAL:SOFAConventions||SimpleFreeFieldHRIR||rm||||attribute||This conventions is for HRIRs recorded under free-field conditions or other IRs created under conditions where room information is irrelevant |- |GLOBAL:SOFAConventionsVersion||0.3||rm||||attribute|| |- |GLOBAL:APIName||||rm||||attribute|| |- |GLOBAL:APIVersion||||rm||||attribute|| |- |GLOBAL:ApplicationName||||m||||attribute|| |- |GLOBAL:ApplicationVersion||||m||||attribute|| |- |GLOBAL:AuthorContact||||m||||attribute|| |- |GLOBAL:Comment||||m||||attribute|| |- |GLOBAL:DataType||FIR||rm||||attribute|| |- |GLOBAL:History||||m||||attribute|| |- |GLOBAL:License||No license provided, ask the author for permission||m||||attribute|| |- |GLOBAL:Organization||||m||||attribute|| |- |GLOBAL:References||||m||||attribute|| |- |GLOBAL:RoomType||free field||m||||attribute|| |- |GLOBAL:Source||||m||||attribute|| |- |GLOBAL:TimeCreated||||m||||attribute|| |- |GLOBAL:TimeModified||||m||||attribute|| |- |GLOBAL:Title||||m||||attribute|| |- |ListenerPosition||[0 0 0] ||m||IC, MC||double|| |- |ListenerPosition:Type||cartesian||m||||attribute|| |- |ListenerPosition:Units||meter||m||||attribute|| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition:Type||cartesian||m||||attribute|| |- |ReceiverPosition:Units||meter||m||||attribute|| |- |SourcePosition||[0 0 1]||m||IC, MC||double||Source position is assumed to vary for different directions/positions around the listener |- |SourcePosition:Type||spherical||m||||attribute|| |- |SourcePosition:Units||degree, degree, meter||m||||attribute|| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition:Type||cartesian||m||||attribute|| |- |EmitterPosition:Units||meter||m||||attribute|| |- |GLOBAL:DatabaseName||||m||||attribute||name of the database to which these data belong |- |GLOBAL:SubjectID||||m||||attribute||ID of the subject from the database |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[1 0 0]||m||IC, MC||double|| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate:Units||hertz||m||||attribute|| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.2 (deprecated) === [[File:SimpleFreeFieldHRIR-0.2.png|right|thumb|225px]] This conventions essentially defines the setup used in the [http://www.kfs.oeaw.ac.at/hrtf ARI], LISTEN, FIU, CIPIC, and other similar HRTF databases. The measurements are done in free field with a single excitation source assuming an omnidirectional loudspeaker. Human listeners are considered and thus, the number of receivers is two. Azimuth and elevation angles are varied and the tilt of the head is not considered during the measurement. The measured HRTFs are represented as FIR filters, with a single HRTF set of a listener per file. * General attributes: SOFAConventions: SimpleFreeFieldHRIR, Datatype: FIR, RoomType: free field, other general attributes... * Source: Source is in the origin of the setup and consists of a single emitter. For default values, SourcePosition: (0 0 0), and EmitterPosition: (0 0 0). SourceUp, SourceView, and SourceRotation are not considered and optional. * Listener: The listener is in the measurement distance X (in meter) from the source, facing the source. For default values, we consider a single distance X, thus, ListenerPosition: (X 0 0), ListenerView: (0 0 0), ListenerUp: (X 0 1). * Receivers: Two receivers (=ears) on a head with radius H (in meter): ReceiverPosition: (0 -H 0; 0 +H 0). * The different azimuth and elevation angles of the measurement are described by the ListenerRotation as [M 3] matrix (in degrees). The coordinate type is [http://en.wikipedia.org/wiki/Axes_conventions DIN 9300]. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL_Conventions||SOFA||rm|||||| |- |GLOBAL_Version||0.4||rm|||||| |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm|||||| |- |GLOBAL_SOFAConventionsVersion||0.2||rm|||||| |- |GLOBAL_APIName||||rm||||||Insert the API Name here |- |GLOBAL_APIVersion||||rm||||||Insert the API Version here |- |GLOBAL_AuthorContact||||m|||||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||||| |- |GLOBAL_Organization||||m|||||| |- |GLOBAL_RoomType||free field||m|||||| |- |GLOBAL_DataType||FIR||rm|||||| |- |GLOBAL_History||||m|||||| |- |GLOBAL_Source||||m|||||| |- |GLOBAL_Title||||m|||||| |- |GLOBAL_References||||m|||||| |- |GLOBAL_Comment||||m|||||| |- |GLOBAL_TimeCreated||||m||||||will be updated when saving and not existing or empty |- |GLOBAL_TimeModified||||m||||||will be updated each time when saving |- |GLOBAL_ApplicationName||||m|||||| |- |GLOBAL_ApplicationVersion||||m|||||| |- |GLOBAL_DatabaseName||||m|||||| |- |GLOBAL_SubjectID||||m|||||| |- |ListenerPosition||[1 0 0] ||m||IC, MC||double|| |- |ListenerPosition_Type||cartesian||m|||||| |- |ListenerPosition_Units||meter||m|||||| |- |ListenerUp||[0 0 1]||m||IC, MC||double|| |- |ListenerView||[-1 0 0]||m||IC, MC||double|| |- |ListenerRotation||[0 0 0]||m||IC, MC||double|| |- |ListenerRotation_Type||din9300||m|||||| |- |ListenerRotation_Units||degrees||m|||||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM||double|| |- |ReceiverPosition_Type||cartesian||m|||||| |- |ReceiverPosition_Units||meter||m|||||| |- |SourcePosition||[0 0 0]||m||IC, MC||double|| |- |SourcePosition_Type||cartesian||m|||||| |- |SourcePosition_Units||meter||m|||||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM||double|| |- |EmitterPosition_Type||cartesian||m|||||| |- |EmitterPosition_Units||meter||m|||||| |- |Data.IR||[1 1]||m||mRn||double|| |- |Data.SamplingRate||48000||m||I||double|| |- |Data.SamplingRate_Units||hertz||m|||||| |- |Data.Delay||[0 0]||m||IR, MR||double|| |} === Version 0.1 (deprecated) === {| border="1" !Name !Default !Flags !Dimensions !Comment |- |GLOBAL_Conventions||SOFA||rm|| || |- |GLOBAL_Version||0.3||rm|| || |- |GLOBAL_SOFAConventions||SimpleFreeFieldHRIR||rm |||| |- |GLOBAL_SOFAConventionsVersion||0.1||m|| || |- |GLOBAL_APIName||*||rm|| ||Insert the API Name here |- |GLOBAL_APIVersion||*||rm || ||Insert the API Version here |- |GLOBAL_ApplicationName||||m |||| |- |GLOBAL_ApplicationVersion||||m |||| |- |GLOBAL_AuthorContact||||m |||| |- |GLOBAL_License||No license provided, ask the author for permission||m|||| |- |GLOBAL_Organization||||m |||| |- |GLOBAL_DatabaseName||||m|||| |- |GLOBAL_SubjectID||||m |||| |- |GLOBAL_RoomType||free field||m|||| |- |GLOBAL_DataType||FIR||m|||| |- |GLOBAL_History|||||||| |- |GLOBAL_Comment|||||||| |- |GLOBAL_DatabaseTimeCreated||*||m|||| will be updated when saving and not existing or empty |- |GLOBAL_DatabaseTimeModified||*||m ||||will be updated each time when saving |- |I||1||rm||I|| |- |I_LongName||singleton dimension||rm|| || |- |R||2||rm||R|| |- |R_LongName||number of receivers||rm|||| |- |E||1||rm||E|| |- |E_LongName||number of emitters||rm|||| |- |N|| - ||m||N|| |- |N_LongName||time||m|| || |- |N_Units||samples||m|| || |- |M|| - ||m||M|| |- |M_LongName||number of measurements||rm |||| |- |C||3||rm||C|| |- |C_LongName||coordinate triplet||rm|||| |- |ListenerPosition|| [1 0 0] ||m||IC, MC|| |- |ListenerPosition_Type||cartesian||m|| || |- |ListenerPosition_Unitsmeter||||m|||| |- |ListenerUp||[1.2 0 1]||m||IC, MC|| |- |ListenerUp_Type||cartesian||m|||| |- |ListenerUp_Units||meter||m|||| |- |ListenerView||[0 0 0]||m||IC, MC|| |- |ListenerView_Type||cartesian||m|||| |- |ListenerView_Units||meter||m|||| |- |ListenerRotation||[0 0 0]||m||IC, MC|| |- |- |ListenerRotation_Type||din9300||m|||| |- |ListenerRotation_Units||degrees||m |||| |- |ReceiverPosition||[0 -0.09 0; 0 0.09 0]||m||rCI, rCM|| |- |ReceiverPosition_Type||cartesian||m|||| |- |ReceiverPosition_Units||meter||m |||| |- |SourcePosition||[0 0 0]||m||IC, MC|| |- |SourcePosition_Type||cartesian||m|||| |- |SourcePosition_Units||meter||m |||| |- |SourceUp||[0 0 1]||m||IC, MC|| |- |SourceUp_Type||cartesian||m|||| |- |SourceUp_Units||meter||m|||| |- |SourceView||[1 0 0]||m||IC, MC|| |- |SourceView_Type||cartesian||m|||| |- |SourceView_Units||meter||m|||| |- |EmitterPosition||[0 0 0]||m||eCI, eCM|| |- |EmitterPosition_Type||cartesian||m|||| |- |EmitterPosition_Units||meter||m |||| |- |Data.IR||[1 1]||m||mRn|| |- |Data.SamplingRate||48000||m||I|| |- |Data.SamplingRate_Units||hertz||m|||| |} 112c4838b1760dbcfd348561f47df98cbf41514f 0 536 2569 2485 2024-04-05T12:57:26Z Isfmiho 3 wikitext text/x-wiki This convention set defines a setup used for measuring Spatial room impulse responses (SRIRs) in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of receivers (e.g., a microphone array). The data is represented as FIR filters and the positions of both the source and the listener may vary. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. The conventions is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:RoomShortName||<nowiki></nowiki>||||||attribute||Short name of the Room |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||Informal verbal description of the room |- |GLOBAL:RoomLocation||<nowiki></nowiki>||||||attribute||Location of the room |- |GLOBAL:RoomGeometry||<nowiki></nowiki>||||||attribute||URI to a file describing the room geometry. |- |RoomTemperature||<nowiki>0</nowiki>||||I, M||double||Temperature during measurements, given in Kelvin. |- |RoomTemperature:Units||<nowiki>kelvin</nowiki>||||||attribute||Units of the room temperature. |- |RoomVolume||<nowiki>0</nowiki>||||I, M||double||Volume of the room. |- |RoomVolume:Units||<nowiki>cubic metre</nowiki>||||||attribute||Units of the room volume. |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverDescriptions||<nowiki>{''}</nowiki>||||RS, RSM||string||R-dependent version of the attribute ReceiverDescription |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||ES, ESM||string||E-dependent version of the attribute EmitterDescription |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} d34bc0c79f0b736d54c9243da47398b3ff704fda 2570 2569 2024-04-08T07:22:39Z Isfmiho 3 wikitext text/x-wiki This convention set defines a setup used for measuring Spatial room impulse responses (SRIRs) in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of receivers (e.g., a microphone array). The data is represented as FIR filters and the positions of both the source and the listener may vary. SingleRoomSRIR is the standardized version of the previously proposed [[SingleRoomDRIR]]. == Version 1.1 == The conventions' version is defined in AES69-2022 (SOFA 2.1). {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.1</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:RoomShortName||<nowiki></nowiki>||||||attribute||Short name of the Room |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||Informal verbal description of the room |- |GLOBAL:RoomLocation||<nowiki></nowiki>||||||attribute||Location of the room |- |GLOBAL:RoomGeometry||<nowiki></nowiki>||||||attribute||URI to a file describing the room geometry. |- |RoomTemperature||<nowiki>0</nowiki>||||I, M||double||Temperature during measurements, given in Kelvin. |- |RoomTemperature:Units||<nowiki>kelvin</nowiki>||||||attribute||Units of the room temperature. |- |RoomVolume||<nowiki>0</nowiki>||||I, M||double||Volume of the room. |- |RoomVolume:Units||<nowiki>cubic metre</nowiki>||||||attribute||Units of the room volume. |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverDescriptions||<nowiki>{''}</nowiki>||||MS, RS, MRS||string||M- and/or R-dependent version of the attribute ReceiverDescription with specific descriptions of the receivers. |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||MS, ES, MES||string||M- and/or E-dependent version of the attribute EmitterDescription with |- |specific descriptions of the emitters||<nowiki></nowiki>|||||||| |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} == Version 1.0 == Version 1.0 is deprecated. Please use the updated version instead. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SingleRoomSRIR</nowiki>||rm||||attribute||For measuring SRIRs in a single room with a single excitation source (e.g., a loudspeaker) and a listener containing an arbitrary number of omnidirectional receivers (e.g., a microphone array). |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>FIR</nowiki>||rm||||attribute||Shall be FIR |- |GLOBAL:RoomType||<nowiki>shoebox</nowiki>||m||||attribute||Shall be 'shoebox' or 'dae' |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:RoomShortName||<nowiki></nowiki>||||||attribute||Short name of the Room |- |GLOBAL:RoomDescription||<nowiki></nowiki>||||||attribute||Informal verbal description of the room |- |GLOBAL:RoomLocation||<nowiki></nowiki>||||||attribute||Location of the room |- |GLOBAL:RoomGeometry||<nowiki></nowiki>||||||attribute||URI to a file describing the room geometry. |- |RoomTemperature||<nowiki>0</nowiki>||||I, M||double||Temperature during measurements, given in Kelvin. |- |RoomTemperature:Units||<nowiki>kelvin</nowiki>||||||attribute||Units of the room temperature. |- |RoomVolume||<nowiki>0</nowiki>||||I, M||double||Volume of the room. |- |RoomVolume:Units||<nowiki>cubic metre</nowiki>||||||attribute||Units of the room volume. |- |RoomCornerA||<nowiki>[0 0 0]</nowiki>||||IC, MC||double|| |- |RoomCornerB||<nowiki>[1 2 3]</nowiki>||||IC, MC||double|| |- |RoomCorners||<nowiki>0</nowiki>||||II||double||The value of this attribute is to be ignored. It only exist to for RoomCorners:Type and RoomCorners:Units |- |RoomCorners:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |RoomCorners:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:ListenerShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ListenerDescription||<nowiki></nowiki>||||||attribute|| |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||MC||double|| |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:ReceiverShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ReceiverDescription||<nowiki></nowiki>||||||attribute|| |- |ReceiverDescriptions||<nowiki>{''}</nowiki>||||RS, RSM||string||R-dependent version of the attribute ReceiverDescription |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RCI, RCM||double|| |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Can be of any type enabling both spatially discrete and spatially continuous representations. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverView||<nowiki>[1 0 0]</nowiki>||||RCI, RCM||double|| |- |ReceiverUp||<nowiki>[0 0 1]</nowiki>||||RCI, RCM||double|| |- |ReceiverView:Type||<nowiki>cartesian</nowiki>||||||attribute|| |- |ReceiverView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |GLOBAL:SourceShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:SourceDescription||<nowiki></nowiki>||||||attribute|| |- |SourcePosition||<nowiki>[0 0 1]</nowiki>||m||MC||double|| |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double|| |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double|| |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |GLOBAL:EmitterShortName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||ES, ESM||string||E-dependent version of the attribute EmitterDescription |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI, eCM||double|| |- |EmitterPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |EmitterView||<nowiki>[1 0 0]</nowiki>||||ECI, ECM||double|| |- |EmitterUp||<nowiki>[0 0 1]</nowiki>||||ECI, ECM||double|| |- |EmitterView:Type||<nowiki>cartesian</nowiki>||||||attribute||Shall be 'cartesian' or 'spherical', restricting to spatially discrete emitters. |- |EmitterView:Units||<nowiki>metre</nowiki>||||||attribute|| |- |Data.IR||<nowiki>0</nowiki>||m||mrn||double||Impulse responses |- |Data.SamplingRate||<nowiki>48000</nowiki>||m||I, M||double||Sampling rate of the samples in Data.IR and Data.Delay |- |Data.SamplingRate:Units||<nowiki>hertz</nowiki>||m||||attribute||Unit of the sampling rate |- |Data.Delay||<nowiki>0</nowiki>||m||IR, MR||double||Additional delay of each IR (in samples) |- |MeasurementDate||<nowiki>0</nowiki>||||M||double||Optional M-dependent date and time of the measurement |} c804dc5d5876cc4fcd0830f717255c50d592f3b6 0 498 2601 2464 2024-10-07T08:51:33Z Isfmiho 3 /* Version 1.1 */ wikitext text/x-wiki == Description == FreeFieldDirectivityTF is a convention for storing directivity of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes. We consider free-field directivites only, i.e., assuming that a potential room has no effect on the data. We consider musical notes as a parameter directly addressing musical instruments. The applications can be: * '''Musical acoustics:''' When measuring of directivity of instruments, this convention can be used for storing the directivity data, which then can be used for general research in musical acoustics. * '''Room-acoustic simulations:''' When rendering acoustic scenes combined with simulations of the room acoustics, this convention can provide the directivity data for more realistic auralizations. A simple setting assumes that the acoustic source under consideration is surrounded by many microphones capturing the signal emitted by the source from different spatial directions. To this end, we define the following: * '''Source''' represents the acoustic source under consideration. * '''Emitters''' A single Emitter is considered that is collocated with the source. * '''Receivers''' represent the microphones capturing the sound from the acoustic source * '''Listener''' represents the array of microphones. In a simple setting, the position of the Listener is collocated with the position of the Source. * '''Data''' stores the captured signals. The data is saved as complex numbers in Data.Real and Data.Imag at the N spectral frequencies for R receivers and M measurements. * '''TuningFrequency''' describes the tuning frequency the instrument is tuned to (in Hertz). * '''MIDINote''' describes the note the acoustic source was playing. The note is specified as MIDI notes according to the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specification, version 1.0]. Note that a note of 69 refers to A4, which corresponds to the frequency specified by TuningFrequency. Note also that both TuningFrequency and MIDINote can be omitted when not required, e.g., for atonal sources such as loudspeakers. * '''Measurement''' captures a modification of the directivity condition: ** Modified orientation of the microphone array during the measurement? The ListenerView and ListenerUp will change. ** Another musical note played during the measurement? The MIDINote will change. ** Another direction of the directivity required for auralization? Search for the proper ReceiverPosition (in a postprocessed dataset with a single ListenerView) or for a spatial superposition of ListenerView, ListenerUp, and ReceiverPosition (in a dataset with raw measurements). '''Examples for the data representation of musical sources:''' * '''Full spectrum and atonal instrument:''' The directivity of a cymbal, saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. The played notes refer to different playing styles of the cymbal (different strength or hitting locations). Data.N represents the frequencies which are identical for each Measurement such as played note and direction. * '''Full spectrum and tonal instrument:''' Signal of a violin (single tones, scales, or complete pieces), saved as a discrete single-sided spectrum for equidistant frequencies between 0 Hz and the Nyquist frequency. Data.N represents the frequencies which are identical for each measured condition. Such data are raw data from which directivities can be computed in a post-processing step. * '''Fractional octave spectrum:''' The directivity of a violin, with the spectrum represented by a few N fractional octaves. Data.N represents frequencies which are identical for each Measurement such as played note and direction. The data are post processed such that the spatial parameters of the Source and Listener are constant and the directivity is encoded in ReceiverPosition only. This format is intended to be used by room-acoustic simulations. Note that is might simplify the original representation of the measurement. * '''Moving instrument:''' The influence of the musician on the directivity of the musician and/or the instrument. To this end, the spatial relation between the musician/instrument (=Source) and the microphones (Listener/Receivers) is important and thus represented in the metadata. The data can be captured by repeated recordings of the same note/scale/piece for different positions of the listener/instrument. Note that this is a complex scenario and thus yield a complex representation. In all the above cases, there is no connection between the number of emitters and measurements. The number of emitters will most likely be e=1, but can have other values, for example if the positions where a cymbal was hit should be described in detail. '''Examples for the data representation of loudspeakers:''' * '''Two-way loudspeaker:''' Directivity of a two-way speaker, i.e., the low-frequency unit (emitter) and mid/high-frequency unit are measured separately. In this case, the number of emitters remains e=1, but the number of measurements is m=2. The EmitterPosition and EmitterDescription can be of size [mC] and [mS]. If the two units are measured together the number of measurements will be m=1. Additional metadata is considered to more coherently describe the dataset: * '''SourcePosition:Reference''', '''SourceView:Reference''', and '''SourceUp:Reference''' provide a narrative description about the spatial reference of the source, e.g. for the trumpet, 'The bell', 'Viewing direction of the bell', and 'Along the keys, keys up' for SourcePosition:Reference, SourceView:Reference, and SourceUp:Reference, respectively. Mandatory in order to provide a reference across different instruments. * '''Description''' provides a narrative description of each measurement, which is highly recommend for documenting the data. This might be the note, the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. NoteDescription is optional and can be provided individually for each Measurement when required. * '''GLOBAL:Musician''' provides a narrative description of the musician such as position, behavior, or personal data if not data-protected. == Version 1.1 == This version uses SOFA 2.1 which reflects the AES69-2022 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.1</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or '2-way loudspeaker' |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or 'LoudspeakerCompany' |- |GLOBAL:EmitterDescription||<nowiki></nowiki>||||||attribute||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., 'The bell' for a trumpet or 'On the front plate between the low- and mid/high-frequency unit' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., 'Viewing direction of the bell' for a trumpet or 'Perpendicular to the front plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., 'Along the keys, keys up' for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eC, eCM||double||Position. In a simple settings, a single emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescriptions||<nowiki>{''}</nowiki>||||MS, ES, MES||string||A more detailed description of the Emitters. For example, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Descriptions||<nowiki>{''}</nowiki>||||MS||string||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki>440</nowiki>||||I, M||double||Frequency (in hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute||narrative name of N |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Units used for N |} == Version 1.0 == This version uses SOFA 2.0 which reflects the AES69-2020 standard. {| border="1" !Name !Default ![[SOFA_conventions#AnchorFlags|Flags]] ![[SOFA_conventions#AnchorDimensions|Dimensions]] !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>2.1</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |GLOBAL:Description||<nowiki></nowiki>||||||attribute||Narrative description of a measurement. For musical instruments/singers, the note (C1, D1, etc) or the dynamic (pp., ff., etc), or the string played, the playing style (pizzicato, legato, etc.), or the type of excitation (e.g., hit location of a cymbal). For loudspeakers, the system and driver units. |- |GLOBAL:SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or '2-way loudspeaker' |- |GLOBAL:SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or 'LoudspeakerCompany' |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||IC, RC, RCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, 'The bell'. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, 'Viewing direction of the bell'. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, 'Along the keys, keys up'. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |EmitterDescription||<nowiki>{''}</nowiki>||||IS, MS||string||A more detailed structure of the source. In a simple setting, a single Emitter is considered that is collocated with the source. In a more complicated setting, this may be the strings of a violin or the units of a loudspeaker. |- |MIDINote||<nowiki>0</nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki>{''}</nowiki>||||MS||string||This variable is used when the description varies with M. |- |SourceTuningFrequency||<nowiki>440</nowiki>||||I, M||double||Frequency (in hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote=69). Recommended for tonal instruments. |- |Data.Real||<nowiki>0</nowiki>||m||mrn||double||Real part of the complex spectrum. The default value 0 indicates that all data fields are initialized with zero values. |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||Imaginary part of the complex spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequency values |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>hertz</nowiki>||m||||attribute||Units used for N |} == Version 0.2 == This version uses the more general Object metadata (instead of NoteDescription). It was considered to rename the Conventions to "SimpleFreeFieldDirectivityTF" but the change was discarded and will be called "FreeFieldDirectivityTF" from version 1.0 again (according to SOFA standard). {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>SimpleFreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.2</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DatabaseName||<nowiki></nowiki>||m||||attribute||Name of the database. Used for classification of the data. |- |GLOBAL:Musician||<nowiki></nowiki>||||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerDescription||||||||attribute||Description of the listener. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| Type of the coordinate system used. |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ListenerView||<nowiki>[1 0 0]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |ListenerUp||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |ListenerView:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used for listener view/up. |- |ListenerView:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |ReceiverPosition||<nowiki>[0 0 1]</nowiki>||m||rCI, rCM||double||Positions of the receiver(s). |- |ReceiverPosition:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used. |- |ReceiverPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin', 'Female singer', or ‘2-way loudspeaker’ |- |SourceManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' or ‘LoudspeakerCompany’ |- |SourceTuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) to which a musical instrument is tuned to corresponding to the note A4 (MIDINote = 69). Not mandatory, but recommended for tonal instruments. |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., ‘The bell’ for a trumpet or ‘On the front plate between the low- and mid/high-frequency unit’ for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||View vector for the orientation. |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector for the orientation. |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute||Type of the coordinate system used for source view/up. |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., ‘Viewing direction of the bell’ for a trumpet or 'Perpendicular to the front plate`for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., ‘Along the keys, keys up’ for a trumpet or 'Perpendicular to the top plate' for a loudspeaker. Mandatory in order to provide a reference across different sources. |- |EmitterDescription||||||IS, MS||string||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||IC, MC||double||Position. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute||Type of the coordinate system used. |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute||Units of the coordinates. |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the MIDI specifications, version 1.0 (https://www.midi.org/specifications-old/item/the-midi-1-0-specification). Not mandatory, but recommended for tonal instruments. |- |Description||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a measurement (recommend for documenting the data). For musical instruments/singers: The note (C1, D1, etc), the dynamic (pp., ff., etc), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. For loudspeakers: The unit (low, mid, higg, etc). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} == Version 0.1 == This version uses SOFA 1.0 which reflects the AES69-2015 standard. {| border="1" !Name !Default !Flags !Dimensions !Type !Comment |- |GLOBAL:Conventions||<nowiki>SOFA</nowiki>||rm||||attribute|| |- |GLOBAL:Version||<nowiki>1.0</nowiki>||rm||||attribute|| |- |GLOBAL:SOFAConventions||<nowiki>FreeFieldDirectivityTF</nowiki>||rm||||attribute||This conventions stores directivities of acoustic sources (instruments, loudspeakers, singers, talkers, etc) in the frequency domain for multiple musical notes in free field. |- |GLOBAL:SOFAConventionsVersion||<nowiki>0.1</nowiki>||rm||||attribute|| |- |GLOBAL:APIName||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:APIVersion||<nowiki></nowiki>||rm||||attribute|| |- |GLOBAL:ApplicationName||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:ApplicationVersion||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:AuthorContact||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Comment||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DataType||<nowiki>TF</nowiki>||rm||||attribute||We store frequency-dependent data here |- |GLOBAL:History||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:License||<nowiki>No license provided, ask the author for permission</nowiki>||m||||attribute|| |- |GLOBAL:Organization||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:References||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:RoomType||<nowiki>free field</nowiki>||m||||attribute||The room information can be arbitrary, but the spatial setup assumes free field. |- |GLOBAL:Origin||<nowiki></nowiki>||||||attribute|| |- |GLOBAL:DateCreated||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:DateModified||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:Title||<nowiki></nowiki>||m||||attribute|| |- |GLOBAL:InstrumentType||<nowiki></nowiki>||m||||attribute||Narrative description of the acoustic source, e.g., 'Violin' or 'Human' |- |GLOBAL:InstrumentManufacturer||<nowiki></nowiki>||m||||attribute||Narrative description of the manufacturer of the source, e.g., 'Stradivari, Lady Blunt, 1721' |- |GLOBAL:Musician||<nowiki></nowiki>||m||||attribute||Narrative description of the musician such as position, behavior, or personal data if not data-protected, e.g., 'Christiane Schmidt sitting on the chair', or 'artificial excitation by R2D2'. |- |ListenerPosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the microphone array during the measurements. |- |ListenerPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ListenerPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |ListenerView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the microphone array |- |ListenerView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ListenerUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the microphone array |- |ListenerUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |ListenerUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |ReceiverPosition||<nowiki>[0 0 0]</nowiki>||m||rCI, rCM||double||Positions of the microphones during the measurements (relative to the Listener) |- |ReceiverPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |ReceiverPosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition||<nowiki>[0 0 0] </nowiki>||m||IC, MC||double||Position of the acoustic source (instrument) |- |SourcePosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |SourcePosition:Units||<nowiki>metre</nowiki>||m||||attribute|| |- |SourcePosition:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source position, e.g., for the trumpet, ‘The bell’. Mandatory in order to provide a reference across different instruments |- |SourceView||<nowiki>[0 0 1]</nowiki>||m||IC, MC||double||Orientation of the acoustic source (instrument) |- |SourceView:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceView:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceView:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source view, e.g., for the trumpet, ‘Viewing direction of the bell’. Mandatory in order to provide a reference across different instruments |- |SourceUp||<nowiki>[0 90 1]</nowiki>||m||IC, MC||double||Up vector of the acoustic source (instrument) |- |SourceUp:Type||<nowiki>spherical</nowiki>||m||||attribute|| |- |SourceUp:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |SourceUp:Reference||<nowiki></nowiki>||m||||attribute||Narrative description of the spatial reference of the source up, e.g., for the trumpet, ‘Along the keys, keys up’. Mandatory in order to provide a reference across different instruments |- |EmitterPosition||<nowiki>[0 0 0]</nowiki>||m||eCI||double||A more detailed structure of the Source. In a simple settings, a single Emitter is considered that is collocated with the source. |- |EmitterPosition:Type||<nowiki>cartesian</nowiki>||m||||attribute|| |- |EmitterPosition:Units||<nowiki>degree, degree, metre</nowiki>||m||||attribute|| |- |MIDINote||<nowiki></nowiki>||||I, M||double||Defines the note played by the source during the measurement. The note is specified a MIDI note by the [https://www.midi.org/specifications-old/item/the-midi-1-0-specification MIDI specifications, version 1.0]. Not mandatory, but recommended for tonal instruments. |- |MIDINoteDescription||<nowiki></nowiki>||||IS, MS||attribute||Narrative description of a note (recommend for documenting the data), e.g., the musical dynamic (pp., ff., etc.), the string on which the note was played, the playing style (pizzicato, legato, etc.), or the location at which a cymbal was hit. |- |TuningFrequency||<nowiki></nowiki>||||I, M||double||Defines the frequency (in Hertz) the instrument is tuned to during the measurements corresponding to the note A4 (MIDINote = 69). |- |Data.Real||<nowiki>0</nowiki>||m||mRn||double||The real part of the complex-valued spectrum |- |Data.Imag||<nowiki>0</nowiki>||m||MRN||double||The imaginary part of the complex-valued spectrum |- |N||<nowiki>0</nowiki>||m||N||double||Frequencies of the considered spectral bands |- |N:LongName||<nowiki>frequency</nowiki>||m||||attribute|| |- |N:Units||<nowiki>Hertz</nowiki>||m||||attribute||Unit of the values given in N |} 3b8dece7716ceed440267174df292a6fa2f4a0ca 0 17 2603 2602 2024-11-12T09:14:40Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave] == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. bcc37fafdaddd04279e4d0a935407f0ecb7fce43 2604 2603 2024-11-26T14:07:56Z Petibub 4 SOFA API MO Test Files --> Archived wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN]: HpIRs of the FABIAN mannequin. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. d5b23e9ec66c40f37d1a4aa189167aca53d3caa7 2605 2604 2025-01-07T10:24:43Z Isfmiho 3 /* Headphone impulse responses (HpIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. b9ed056e4acabca0684ae92a91226db6fea057da 2606 2605 2025-01-07T10:31:23Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 4a3e93d830cf703da99c1815b64b9f04ba025b2e 2607 2606 2025-01-07T10:36:35Z Isfmiho 3 /* Headphone impulse responses (HpIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * '''New:''' [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. b88ae5555e80e6785bd2ca28411e120d5425d8c3 2608 2607 2025-01-07T10:36:52Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. e3419752d0a72127df4e2e3ccc4336efd7ace0bd 2609 2608 2025-01-07T10:37:03Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. a3f7fc5d0886195d55719caaefaa99dbfdcda20d 2610 2609 2025-01-07T10:41:26Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. b99d138bb68a6c05a29695132148fe393b186c8a 2611 2610 2025-01-07T10:42:00Z Isfmiho 3 /* Special HRTFs */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 62945ea7e2d951161f5de04e09a2e3ac049c61c2 2613 2611 2025-01-07T10:48:47Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. e363701706ef319cf62ce0c6f203b76a9ab0b904 2614 2613 2025-01-07T10:48:59Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 322ad4a00335113710063987669167d1fab9298a 2615 2614 2025-01-07T10:49:10Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. ee33c9891474f2490a11e830078a7316bc6620f5 2616 2615 2025-01-07T10:49:59Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. f963064e7160fdb20cfd13cdb4e2086f5d431286 2617 2616 2025-01-07T13:28:13Z Isfmiho 3 /* General purpose free-field databases (HRTFs, PRTFs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 9334fbcfff3e32533181ecc4868f8f257d7e6b8e 2618 2617 2025-01-07T13:28:23Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. b3c0ed7db6ba881fc193a00cbb003b4adb2c7cb5 2620 2618 2025-01-07T14:04:57Z Isfmiho 3 /* Standard (in-the-ear canal) HRTFs of humans */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. d208ba86e2b34f76622b2322ddebd81fa77c029d 2621 2620 2025-01-07T14:07:04Z Isfmiho 3 /* Headphone impulse responses (HpIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 4b575c32303825c3bd09ad27d62736d0e60669bc 2623 2621 2025-01-08T06:08:06Z Isfmiho 3 /* Standard (in-the-ear canal) HRTFs of humans */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 82f81faa519a1254d01046846382cba8cb561225 2624 2623 2025-01-08T06:08:24Z Isfmiho 3 /* Special HRTFs */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 92da525de783435f76585c601f1dfa3c3ad94f18 2625 2624 2025-01-09T07:05:14Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 43ffea741c122cbb51c20e9f5d6bc1010239a0a8 2626 2625 2025-02-05T14:18:51Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * '''New:''' [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' * '''New:''' [https://sofacoustics.org/data/database/dEchorate/ dEchorate dataset]: Multichannel Room Impulse Responses (RIRs), including annotations of early echo timings and 3D positions of microphones, real sources and image sources under different wall configurations in a cuboid room. For description, see [https://zenodo.org/records/4626590 here]. ''(Credit: Diego Di Carlo, Padua)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. ce9a340da61ab41e07421941e35a8b15ba873e5c 2631 2626 2025-03-19T07:29:39Z Isfmiho 3 /* Standard (in-the-ear canal) HRTFs of humans */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2/ SS2]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing in-the-ear HRTFs of 78 listeners. [https://sofacoustics.org/data/database/ss2%20(repeated)/ SS2 (repeated measurements)] contains re-measurements of 8 subjects, for repeatability analysis. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' * '''New:''' [https://sofacoustics.org/data/database/dEchorate/ dEchorate dataset]: Multichannel Room Impulse Responses (RIRs), including annotations of early echo timings and 3D positions of microphones, real sources and image sources under different wall configurations in a cuboid room. For description, see [https://zenodo.org/records/4626590 here]. ''(Credit: Diego Di Carlo, Padua)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 2ca078182653f70608666bfcc4750dfc5cf2ad2f 2632 2631 2025-03-19T07:32:09Z Isfmiho 3 /* HRTFs of artificial heads */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2/ SS2]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing in-the-ear HRTFs of 78 listeners. [https://sofacoustics.org/data/database/ss2%20(repeated)/ SS2 (repeated measurements)] contains re-measurements of 8 subjects, for repeatability analysis. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2%20(mannequins)/ SS2 (mannequins)]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing repeated measurements of KEMAR, B&K HATS and KU100 mannequins. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. * '''New:''' [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' * '''New:''' [https://sofacoustics.org/data/database/dEchorate/ dEchorate dataset]: Multichannel Room Impulse Responses (RIRs), including annotations of early echo timings and 3D positions of microphones, real sources and image sources under different wall configurations in a cuboid room. For description, see [https://zenodo.org/records/4626590 here]. ''(Credit: Diego Di Carlo, Padua)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 614a60a2ddb99bf2af3156ae48800db81ca3da40 2633 2632 2025-03-19T07:32:20Z Isfmiho 3 /* Special HRTFs */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2/ SS2]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing in-the-ear HRTFs of 78 listeners. [https://sofacoustics.org/data/database/ss2%20(repeated)/ SS2 (repeated measurements)] contains re-measurements of 8 subjects, for repeatability analysis. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2%20(mannequins)/ SS2 (mannequins)]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing repeated measurements of KEMAR, B&K HATS and KU100 mannequins. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. * [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' * '''New:''' [https://sofacoustics.org/data/database/dEchorate/ dEchorate dataset]: Multichannel Room Impulse Responses (RIRs), including annotations of early echo timings and 3D positions of microphones, real sources and image sources under different wall configurations in a cuboid room. For description, see [https://zenodo.org/records/4626590 here]. ''(Credit: Diego Di Carlo, Padua)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. dfd47b4b2bfe8196651a4ce1a71048cb5950ae2e 2634 2633 2025-03-19T07:32:30Z Isfmiho 3 /* Room impulse responses databases (DRIRs, SRIRs, BRIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2/ SS2]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing in-the-ear HRTFs of 78 listeners. [https://sofacoustics.org/data/database/ss2%20(repeated)/ SS2 (repeated measurements)] contains re-measurements of 8 subjects, for repeatability analysis. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2%20(mannequins)/ SS2 (mannequins)]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing repeated measurements of KEMAR, B&K HATS and KU100 mannequins. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. * [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' * [https://sofacoustics.org/data/database/dEchorate/ dEchorate dataset]: Multichannel Room Impulse Responses (RIRs), including annotations of early echo timings and 3D positions of microphones, real sources and image sources under different wall configurations in a cuboid room. For description, see [https://zenodo.org/records/4626590 here]. ''(Credit: Diego Di Carlo, Padua)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * '''New:''' [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 8de861372c8203db5c58660715aa592905aa5074 2635 2634 2025-03-19T07:32:39Z Isfmiho 3 /* Headphone impulse responses (HpIRs) */ wikitext text/x-wiki The [http://sofacoustics.org/data main SOFA repository] aims at collect the worldwide available HRTFs, BRIRs, DRIRs, and other SOFA-related data at a single place. It is just in the process of being created: Partial download, metadata access, and database search is not available (yet, we are investigating the possibility of using [http://www.opendap.org/ OPeNDAP] for SOFA repositories). Currently, the data can be accessed and downloaded as they are and the metadata are provided in the particular files. == General purpose free-field [http://sofacoustics.org/data/database databases] (HRTFs, PRTFs) == ===Standard (in-the-ear canal) HRTFs of humans=== * [http://sofacoustics.org/data/database/ari ARI]: HRTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. In-the-ear HRTFs and DTFs for over 220 listeners. ** hrtf, dtf: HRTFs and DTFs, respectively, equalized between 300 Hz and 18 kHz ** hrtf b/c/d, dtf b/c/d: HRTFs and DTFs, equalized between 50 Hz and 18 kHz for hi-fi auralizations ("b" vs. "c" and "d" differ each other in their starting positions and the order of measurement positions: b: 0°→0°, c/d: 270°→270°; subject being rotated clockwise ↻; "c" measurements were recorded until 2023 in the ARI lab in Wohllebengasse, "d" measuremens are recorded in the new ARI lab in Postsparkasse since 2024). * [http://sofacoustics.org/data/database/ari%20(altb) ARI (ALTB)]: HRTFs from the ARI database. Measurements for some of the listeners from the ARI database, repeated and evaluated a few years later, see [http://www.researchgate.net/publication/236111930_Sound_localization_in_individualized_and_non-individualized_crosstalk_cancellation_systems Majdak et al. (2013)]. * [http://sofacoustics.org/data/database/ari%20(las)/ ARI (LAS)]: In-the-ear HRTFs and DTFs are measured in the ARI loudspeaker array studio (LAS). Each file contains HRTFs measured at 451 sound-source directions (91 directions as in [https://doi.org/10.3389/fnins.2023.1027827 McLachlan et al. (2023)]); but extended to 451 directions by rotating the listener four times). * [http://sofacoustics.org/data/database/cipic CIPIC]: HRTFs from the [https://www.ece.ucdavis.edu/cipic/spatial-sound/hrtf-data/ CIPIC database]. 45 listeners, partially [https://sofacoustics.org/data/database/cipic/anthropometry.zip anthropometric data] available. * [http://sofacoustics.org/data/database/riec RIEC]: Far-field HRTFs from the [http://www.riec.tohoku.ac.jp/pub/hrtf/index.html RIEC] database from the Advanced Acoustic Information Systems Laboratory, Research Institute of Electrical Communication, Tohoku University, Japan of over 100 human listeners. ''(Credit: Kanji Watanabe, Japan)'' * [http://sofacoustics.org/data/database/aachen Aachen]: HRTFs from the [http://www.akustik.rwth-aachen.de/go/id/lsly Aachen HRTF database], combined with anthropometric data and 3D ear models of 48 listeners. See the [http://gershwin.akustik.rwth-aachen.de/hrtf/hrtf-lic.php license]. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution)/ Aachen: High-resolution HRTFs] from the [https://publications.rwth-aachen.de/record/793261 Aachen HRTF database], combined with a [https://publications.rwth-aachen.de/record/793260 3D model] of one human listener. ''(Credit: Janina Fels, Aachen)'' * [http://sofacoustics.org/data/database/hutubs/ HUTUBS]: HRTFs from the [https://dx.doi.org/10.14279/depositonce-8487 HUTUBS] database containing anthropometric data, headphone impulse responses, and 3D head models from 96 listeners. The database acquisition is detailed in the accompanying [https://doi.org/10.17743/jaes.2019.0024 paper]. ''(Credit: Fabian Brinkmann, Berlin)'' * [http://sofacoustics.org/data/database/chedar/ CHEDAR]: Numerically calculated HRTFs (.sofa) with 3D meshes of the head and pinnae (.ply) and anthropometric data (.mat) provided. For more details, see the [http://sofacoustics.org/data/database/chedar/documentation.pdf documentation]. ''(Credit: Slim Ghorbal, France)'' * [https://sofacoustics.org/data/database/3d3a/ 3D3A]: Measured in-the-ear HRTFs (.sofa) of 38 subjects, and 3D head and torso scans of 31 subjects from the [http://www.princeton.edu/3D3A/HRTFMeasurements.html Princeton 3D3A Database]. ''(Credit: Edgar Choueiri, USA)'' * [https://sofacoustics.org/data/database/bili%20(dtf)/ BiLi]: Measured in-the-ear HRTF files (.sofa) of 56 subjects. Data are available in [https://sofacoustics.org/data/database/bili%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/bili%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/bili%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/crossmod%20(dtf)/ Crossmod]: Measured in-the-ear HRTF files (.sofa) of 24 subjects. Data are available in [https://sofacoustics.org/data/database/crossmod%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/crossmod%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/crossmod%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/listen%20(dtf)/ Listen]: Measured in-the-ear HRTF files (.sofa) of 50 subjects. Data are available in [https://sofacoustics.org/data/database/listen%20(dtf)/ DTF format], raw [https://sofacoustics.org/data/database/listen%20(hrtf)/ HRTF format], and as DTF format in [https://sofacoustics.org/data/database/listen%20(dtf,%20sos)/ SOS data type]. Multiple sampling rates of these data are available on the [http://opendap.ircam.fr/download/ download page] of the [http://bili2.ircam.fr/ IRCAM database]. ''(Credit: Markus Noisternig, Paris)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 18 human subjects (indices H3 to H20). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs and anthropometric data ([https://sofacoustics.org/data/database/scut/AnthropometricParameters.csv CSV] and [https://sofacoustics.org/data/database/scut/AnthropometricParameters.pdf PDF]) of human listeners. ''(Credit: Guangzheng Yu & Yu Lan, China)'' * [http://sofacoustics.org/data/database/axd AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for 200 listeners. More information about the measurement setup and validation can be found [http://www.aes.org/e-lib/browse.cfm?elib=22128 here]. ''(Credit: Lorenzo Picinali, London)'' * [https://sofacoustics.org/data/database/coat%20(hrtf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/database/coat%20(hrtf%20oldenburg)/ COAT Oldenburg]: HRTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2/ SS2]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing in-the-ear HRTFs of 78 listeners. [https://sofacoustics.org/data/database/ss2%20(repeated)/ SS2 (repeated measurements)] contains re-measurements of 8 subjects, for repeatability analysis. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===HRTFs of artificial heads=== * [http://sofacoustics.org/data/database/mit MIT-KEMAR]: HRTFs from [http://sound.media.mit.edu/resources/KEMAR/ MIT of the KEMAR] dummy head. Reference HRTFs used in many publications. * [http://sofacoustics.org/data/database/ari%20(artificial) ARI (ARTIFICIAL)]: HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners: ** NH169: HRTFs, DTFs, and raw data of a printed head of the corresponding human listener ** NH172: HRTFs, DTFs, raw and reference data of the dummy head Neumann KU 100. Also part of Club Fritz, see below. * [http://sofacoustics.org/data/database/thk THK/HRIR_*]: HRTFs of various mannequins provided by the Technische Hochschule Köln (TH Köln, previously Fachhochschule Köln); further details can be found here: ** [https://zenodo.org/record/3928297 Far-field HRTFs]: Gapless data, high spatial resolution HRTFs of Neumann KU 100. Files: HRIR_CIRC360, HRIR_CIRC360RM, HRIR_FULL2DEG, HRIR_L2354, HRIR_L2702.sofa ''(Credit: Benjamin Bernschütz, Germany).'' **[https://zenodo.org/record/4297951 Near-field HRTFs] (HRIR_*_NF*.sofa): High spatial resolution HRTFs of Neumann KU 100 done for various distances ''(Credit: Johannes Arend, Germany)''. **[https://zenodo.org/record/3928465 Head-gear HRTFs of Neumann KU 100 and HEAD acoustics HMS II] (KU100*.sofa, HMSII*.sofa): High spatial resolution HRTFs while wearing various head gears ''(Credit: Christoph Pörschmann, Germany)''. * [http://sofacoustics.org/data/database/scut SCUT]: Near-field HRTFs from SCUT database of the KEMAR (Radius: 0.2 to 1.0 m). ''(Credit: Bosun Xie, China)'' * [http://sofacoustics.org/data/database/tu-berlin TU-Berlin]: ** HRTFs from [http://doi.org/10.5281/zenodo.55418 TU-Berlin of the KEMAR] dummy-head. HRTFs for several distances (>0.5 m). ''(Credit: Hagen Wierstorf, Germany)'' ** HRTFs from [https://depositonce.tu-berlin.de/handle/11303/6153 TU-Berlin of the FABIAN] dummy-head. Acoustically measured and numerically calculated HRTFs. ''(Credit: Fabian Brinkmann, Germany)'' * [http://sofacoustics.org/data/database/clubfritz Club Fritz]: HRTFs of Neumann KU 100 measured as part of the Club Fritz project where many institutions measured the exact same artificial head, see [http://dx.doi.org/10.1109/JSTSP.2015.2400417 Andreopoulou et al, (2015)]. ''(Credit: Brian Katz, France)''. * [http://sofacoustics.org/data/database/viking/ VIKING]: Full-sphere HRTFs (.sofa) from the [https://doi.org/10.5281/zenodo.4160401 Viking database]. KEMAR mannequin with 20 different pairs of artificial silicone pinnae attached, plus a "pinna-less" condition, measured for 1513 different directions. 3D scans of left pinnae are also included (.stl). ''(Credit: Simone Spagnol, Denmark)'' * [http://sofacoustics.org/data/database/aachen%20(high-resolution%20kemar)/ Aachen: High-resolution HRTFs of the KEMAR] dummy head from the [https://publications.rwth-aachen.de/record/807373 Aachen HRTF database], combined with a 3D model of one subject. ''(Credit: Janina Fels, Aachen)'' * [https://sofacoustics.org/data/database/pku-ioa/ PKU-IOA:] High spatial resolution in-the-ear HRTF database of the KEMAR dummy head with distance from 20 cm to 160 cm, including 20, 30, 40, 50, 75, 100, 130, and 160 cm. ''(Credit: Tianshu Qu, China)'' * [https://sofacoustics.org/data/database/sadie/ SADIE]: Measured in-the-ear HRTF files (.sofa) of 2 dummy heads (indices D1, D2). 3D scans area available on the website of the [https://www.york.ac.uk/sadie-project/database.html SADIE II datebase]. ''(Credit: Gavin Kearney and Cal Armstrong, York)'' * [http://sofacoustics.org/data/database/axd%20(kemar) AXD]: HRTFs from the [https://www.axdesign.co.uk/tools-and-devices/sonicom-hrtf-dataset AXD/SONICOM database], for the KEMAR head, for 2 ears. ''(Credit: Lorenzo Picinali, London)'' * [http://sofacoustics.org/data/database/AMU AMU]: HRTFs from 4 dummy heads, measured at 2 distances (40cm and 2m). Details can be found [https://hal.science/hal-03521905/document here]. ''(Credit: Adrien Vidal, Marseille)'' * [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' * '''New:''' [https://sofacoustics.org/data/database/ss2%20(mannequins)/ SS2 (mannequins)]: HRTFs from the [https://facebookresearch.github.io/SS2_HRTF/ Sound Sphere 2 database], containing repeated measurements of KEMAR, B&K HATS and KU100 mannequins. A detailed documentation can be found [https://facebookresearch.github.io/SS2_HRTF/HRTF_Database_AVAR2024_v6.pdf here].''(Credit: Michaela Warnecke, Meta Reality Labs Research, Redmond)'' ===Special HRTFs=== * [http://sofacoustics.org/data/database/ari%20(bte) ARI (BTE)]: Behind-the-ear HRTFs and DTFs from the [https://www.oeaw.ac.at/isf/hrtf ARI database]. * [https://sofacoustics.org/data/database/olhead%20(hrir)/ OlHeaD (HRIR)], [https://sofacoustics.org/data/database/olhead%20(freefieldir)/ OlHeaD (Free-Field)], [https://sofacoustics.org/data/database/olhead%20(difffieldir)/ OlHeaD (Diffuse-Field)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs of 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * [https://sofacoustics.org/data/database/the%20hearpiece%20database/ Hearpiece]: HRTFs from the [https://zenodo.org/records/4280526 Hearpiece database], covering 87 directions, and responses of the drivers, all measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear. The transfer functions were measured in both ears of 25 human subjects and a KEMAR. ''(Credit: Florian Denk, Oldenburg)'' ===PRTFs=== * [http://sofacoustics.org/data/database/widespread Widespread] (Wide dataset of ear shapes and pinna-related transfer functions obtained by random ear drawings): 1005 pinna meshes matched with correspondingly calculated PRTFs from the [https://www.ietr.fr/spip.php?article1618&lang=en FAST team, IETR (CNRS UMR 6164), CentraleSupélec]. The meshes were created by varying principle components obtained from an analysis of 119 pinna meshes of actual listeners. The PRTFs were calculated by means of the boundary-element method for two spatial grids and three distances, see the upcoming publication [http://sofacoustics.org/data/database/widespread/Widespread.pdf (documentation)]. ''(Credit: Corentin Guezenoc, France)''. == Directivities (sources and receivers) == ===Sources=== * [http://sofacoustics.org/data/database/tu-berlin%20(directivity)/ TU-Berlin]: One data set of a 3-way loudspeaker (low- mid- and high-unite) in 10°x10° resolution, and two data sets of a trumpet, recorded with a 32 channel microphone array, from the TU Berlin. ''(Credit: David Ackermann, Germany)'' ===Receivers=== * TBA == Room impulse responses [http://sofacoustics.org/data/database databases] (DRIRs, SRIRs, BRIRs) == RIRs/BRIRs/DRIRs: * [http://sofacoustics.org/data/database/oldenburg Oldenburg] DRIRs from [http://medi.uni-oldenburg.de/hrir/html/download.html Oldenburg]. Recordings in an office under several conditions ''(Credit: Stephan Ewert and Daryl Kelvasa, Germany)''. * [http://sofacoustics.org/data/database/tuburo TuBuRo]: RIRs (from omnidirectional mic) and BRIRs (from KEMAR) recorded with 64-channel loudspeaker array in a room under various absorbing conditions, see [http://dx.doi.org/10.14279/depositonce-87.2 the source], [https://depositonce.tu-berlin.de/bitstream/11303/245.2/11/AdditionalInformation.pdf notes on the file naming] and [https://secure.aes.org/forum/pubs/ebriefs/?elib=17624 Erbes et al. (2015)]. ''(Credit: Vera Erbes, Rostock, Germany)''. * [http://sofacoustics.org/data/database/sbsbrir SBSBRIR]: BRIRs from the [http://www.bbc.co.uk/rd/publications/sbsbrir Salford-BBC dataset] measured in a recording room for 12 loudspeakers, each for 15 head orientations ([http://usir.salford.ac.uk/30868/ details]). ''(Credit: Chris Pike, Salford)''. * [http://sofacoustics.org/data/database/thk THK/DRIR_* and THK/BRIR_*]: DRIRs and BRIRs measured at the WDR broadcast studios with various microphone arrays provided by the Technische Hochschule Köln (TH Köln). For description, see [https://zenodo.org/record/3930833 here]. ''(Credit: Johannes Arend)''. * [https://sofacoustics.org/data/database/room%20transition%20dataset/ Room Transition dataset]: SRIRs capturing the transition between coupled rooms with 101 positions and four coupled room pairs. For description, see [https://doi.org/10.5281/zenodo.4095493 here] ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/6dof%20dataset/ 6DoF dataset]: SRIRs measured in a variable acoustics room with two spherical microphone arrays. For description, see [https://doi.org/10.5281/zenodo.5720723 here]. ''(Credit: Thomas McKenzie, Aalto)''. * [https://sofacoustics.org/data/database/kaist-iem/ KAIST-IEM dataset]: 6 DoF DRIR dataset measured over a dense loudspeaker grid (6DRIR-DL). For description, see [http://www.aes.org/e-lib/browse.cfm?elib=22184 here]. ''(Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz)''. * [https://sofacoustics.org/data/database/bbc%20maida%20vale/ BBC Maida Vale dataset]: 6 DoF DRIR dataset, measured from the BBC Maida Vale Studios, stored in SH format, available as SingleRoomSRIRs and SingleRoomMIMOSRIRs. For description, see [https://doi.org/10.5281/zenodo.10020866 here]. For full paper, see [https://doi.org/10.3390/acoustics4030047 here]. ''(Credit: Gavin Kearney, University of York)''. * [https://sofacoustics.org/data/database/tu-ilmenau%20(rooms)/ TU Ilmenau room configurations dataset]: A high spatial resolution dataset of spatial room impulse responses for different acoustic room configurations, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10450779 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/tu-ilmenau%20(robot)/ TU Ilmenau robot journey dataset]: Spatial room impulse response dataset: A robot's journey through coupled rooms of a reverberant university building, available as SingleRoomSRIR. For description, see [https://zenodo.org/records/10708306 here]. ''(Credit: Stephan Werner, Ilmenau)'' * [https://sofacoustics.org/data/database/pan-ar/ PAN-AR dataset]: dataset of spatial room impulse responses (SRIRs) measured using a spherical microphone array in 4 distinct rooms with different configurations of source and listener positions. In addition to the SOFA files, spherical pictures, planimetries, and ambient noise recordings are also provided. See the related [https://doi.org/10.1145/3678299.3678332 paper] and the [https://doi.org/10.5281/zenodo.13134270 alternate version of PAN-AR as wav files]. ''(Credit: Giorgio Presti and Davide Fantini, Milan)'' * [https://sofacoustics.org/data/database/dEchorate/ dEchorate dataset]: Multichannel Room Impulse Responses (RIRs), including annotations of early echo timings and 3D positions of microphones, real sources and image sources under different wall configurations in a cuboid room. For description, see [https://zenodo.org/records/4626590 here]. ''(Credit: Diego Di Carlo, Padua)'' == Headphone impulse responses (HpIRs) == * [http://sofacoustics.org/data/headphones/ari ARI]: HpIRs of human listeners from the ARI database. Single headphone, five measurements (with repositioned headphone in-between) for over 100 listeners. * [http://sofacoustics.org/data/headphones/btdei BT-DEI]: HpIRs of human listeners from the [http://padva.dei.unipd.it/?page_id=345 BT-DEI] database. 16 listeners, three headphones ''(Credit: Michele Geronazzo, Italy)''. * [https://sofacoustics.org/data/headphones/tu-berlin/ TU-Berlin of the FABIAN]: HpIRs of the [https://depositonce.tu-berlin.de/handle/11303/6153 FABIAN mannequin] database. Acoustically measured for 34 headphones. ''(Credit: Fabian Brinkmann, Germany)''. * [https://sofacoustics.org/data/headphones/olhead%20(hpir)/ OlHeaD (HpIR)]: HRTFs from the [https://uol.de/mediphysik/downloads/hearingdevicehrtfs OlHeaD database], in total covering HRTFs, 13 microphone locations in 6 hearing device styles, 91 directions, of 16 human subjects and 3 dummy heads. ''(Credit: Florian Denk, Oldenburg)'' * [https://sofacoustics.org/data/headphones/coat%20(hptf%20aachen)/ COAT Aachen], [https://sofacoustics.org/data/headphones/coat%20(hptf%20oldenburg)/ COAT Oldenburg]: HpTFs from the [https://zenodo.org/records/4556707 COAT database], measured at two different sites: ITA Aachen, and Universität Oldenburg. ''(Credit: Florian Denk, Oldenburg)'' == Example & Test SOFA Files == * [http://sofacoustics.org/data/examples/ Example files]: SOFA example & test files for stable [[SOFA_conventions|conventions]]; these files are a subset of other databases on this page, renamed according their conventions. * [http://sofacoustics.org/data/sofatoolbox_test sofatoolbox_test]: HRTFs resulting from tests of the [http://sourceforge.net/projects/sofacoustics/ SOFA Toolbox v2.x] * [http://sofacoustics.org/data/sofa_api_mo_test sofa_api_mo_test] (deprecated): HRTFs resulting from tests of the deprecated version of the [http://sourceforge.net/projects/sofacoustics/ SOFA API v1.x for Matlab/Octave]. These files are deprecated and in order to prevent them from being accidentally used, they are available as a zip file archive only. == Other repositories == This is a list of other repositories providing HRTFs, BRIRs, and DRIRs available as SOFA files. * ARI free-field HRTF database. HRTFs available for in-the-ear (ITE) and behind-the-ear (BTE) HRTFs. Link: https://www.oeaw.ac.at/isf/hrtf * Example files created by the Matlab/Octave API. Link: http://tinyurl.com/sofaHRTFs * [https://www.york.ac.uk/sadie-project/database.html SADIE]: Far-field HRTFs from the [https://www.york.ac.uk/sadie-project/ SADIE] project of over 20 human listeners. ''(Credit: Gavin Kearney, York)'' == Database missing? == If you want your/a SOFA database to be added please [https://www.sofaconventions.org/mediawiki/index.php/People_behind_SOFA contact Michael Mihocic or Piotr Majdak] for support. 23a5fe750c5629f21a747423e78e87bdf90cc367 0 1 2612 2600 2025-01-07T10:47:50Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 07.01.2025: OlHeaD: OlHeaD dataset for humans, dummy heads, different hearing aid positions added (Credit: Florian Denk, Oldenburg) * 03.09.2024: PAN-AR: SRIR dataset for different room and configurations added (Credit: Giorgio Presti and Davide Fantini, Milan) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset for different acoustic room configurations added (Credit: Stephan Werner, Ilmenau) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset of a robot's journey through coupled rooms added (Credit: Stephan Werner, Ilmenau) * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Marseille) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 3bc4920f120dc58b1b54ae7b60ee5f1689094443 2619 2612 2025-01-07T13:29:29Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 07.01.2025: Hearpiece: HRTFs covering 87 directions, measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear (Credit: Florian Denk, Oldenburg) * 07.01.2025: OlHeaD: OlHeaD dataset for humans, dummy heads, different hearing aid positions added (Credit: Florian Denk, Oldenburg) * 03.09.2024: PAN-AR: SRIR dataset for different room and configurations added (Credit: Giorgio Presti and Davide Fantini, Milan) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset for different acoustic room configurations added (Credit: Stephan Werner, Ilmenau) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset of a robot's journey through coupled rooms added (Credit: Stephan Werner, Ilmenau) * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Marseille) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 6279e4d52755b439c21000c9fbdeb01fa276cd26 2622 2619 2025-01-07T14:09:02Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 07.01.2025: COAT: HRTFs and HpTFs from the COAT database, measured at ITA Aachen, and Universität Oldenburg (Credit: Florian Denk, Oldenburg) * 07.01.2025: Hearpiece: HRTFs covering 87 directions, measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear (Credit: Florian Denk, Oldenburg) * 07.01.2025: OlHeaD: OlHeaD dataset for humans, dummy heads, different hearing aid positions added (Credit: Florian Denk, Oldenburg) * 03.09.2024: PAN-AR: SRIR dataset for different room and configurations added (Credit: Giorgio Presti and Davide Fantini, Milan) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset for different acoustic room configurations added (Credit: Stephan Werner, Ilmenau) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset of a robot's journey through coupled rooms added (Credit: Stephan Werner, Ilmenau) * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Marseille) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 2317b063dc2cdac6220c59b39cc82665734aba2d 2627 2622 2025-02-05T14:20:53Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 05.02.2025: dEchorate: Multichannel Room Impulse Responses (RIRs) added (Credit: Diego Di Carlo, Padua) * 07.01.2025: COAT: HRTFs and HpTFs from the COAT database, measured at ITA Aachen, and Universität Oldenburg (Credit: Florian Denk, Oldenburg) * 07.01.2025: Hearpiece: HRTFs covering 87 directions, measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear (Credit: Florian Denk, Oldenburg) * 07.01.2025: OlHeaD: OlHeaD dataset for humans, dummy heads, different hearing aid positions added (Credit: Florian Denk, Oldenburg) * 03.09.2024: PAN-AR: SRIR dataset for different room and configurations added (Credit: Giorgio Presti and Davide Fantini, Milan) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset for different acoustic room configurations added (Credit: Stephan Werner, Ilmenau) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset of a robot's journey through coupled rooms added (Credit: Stephan Werner, Ilmenau) * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Marseille) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 15d987889af973c4914f74b2775b2f6b19c0ff4a 2630 2627 2025-03-14T12:45:08Z Isfmiho 3 /* SOFA Toolbox v2.1 has been released. See Software and APIs for details. */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 05.02.2025: dEchorate: Multichannel Room Impulse Responses (RIRs) added (Credit: Diego Di Carlo, Padua) * 07.01.2025: COAT: HRTFs and HpTFs from the COAT database, measured at ITA Aachen, and Universität Oldenburg (Credit: Florian Denk, Oldenburg) * 07.01.2025: Hearpiece: HRTFs covering 87 directions, measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear (Credit: Florian Denk, Oldenburg) * 07.01.2025: OlHeaD: OlHeaD dataset for humans, dummy heads, different hearing aid positions added (Credit: Florian Denk, Oldenburg) * 03.09.2024: PAN-AR: SRIR dataset for different room and configurations added (Credit: Giorgio Presti and Davide Fantini, Milan) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset for different acoustic room configurations added (Credit: Stephan Werner, Ilmenau) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset of a robot's journey through coupled rooms added (Credit: Stephan Werner, Ilmenau) * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Marseille) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released 1fd4d1976456eae3c525d935a4c442d41d5c9e55 2636 2630 2025-03-19T07:34:15Z Isfmiho 3 /* News history */ wikitext text/x-wiki ===[https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] has been released. See [[Software and APIs]] for details.=== SOFA is a file format for storing [http://en.wikipedia.org/wiki/Spatial_sound spatially] oriented acoustic data like [http://en.wikipedia.org/wiki/Head-related_transfer_function head-related transfer functions (HRTFs]) and binaural or spatial room [http://en.wikipedia.org/wiki/Impulse_response impulse responses] (BRIRs, SRIRs). SOFA has been standardized by the [http://aes.org Audio Engineering Society (AES)] as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015] and reaffirmed as [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2020] and [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2022]. This website aims at providing SOFA-relevant information. * [[General information on SOFA]] * [[SOFA specifications]] SOFA conventions are designed for a consistent description of data stored in SOFA. The aim is the exchange of the data between researches and users. For each conventions, data exist from corresponding measurement setups and its description has been accepted by the peer group. Suggestions for new SOFA conventions and additions to existing ones are highly welcome. * [[SOFA conventions]] List of repositories with SOFA files containing [http://en.wikipedia.org/wiki/Head-related_transfer_function HRTFs], PRTFs, BRIRs, and DRIRs measured by different researchers. * [[Files|Files (HRTFs, BRIRs, DRIRs, HpIRs)]] SOFA files can be read and modified by software and application-programming interfaces (APIs). * [[Software and APIs]] SOFA is result of the work of many people from various institutions. * [[People behind SOFA]] The SOFA project got awarded with the Reproducibility in Audio and Music Research Prize 2013 [http://soundsoftware.ac.uk/rr-prize-winner-announcement]. == News history == * 19.03.2025: SS2: HRTFs of 78 humans, and 3 mannequins added (Credit: Michaela Warnecke, Redmond)) * 05.02.2025: dEchorate: Multichannel Room Impulse Responses (RIRs) added (Credit: Diego Di Carlo, Padua) * 07.01.2025: COAT: HRTFs and HpTFs from the COAT database, measured at ITA Aachen, and Universität Oldenburg (Credit: Florian Denk, Oldenburg) * 07.01.2025: Hearpiece: HRTFs covering 87 directions, measured at four microphones of the Hearpiece as well as the eardrum in the occluded and open ear (Credit: Florian Denk, Oldenburg) * 07.01.2025: OlHeaD: OlHeaD dataset for humans, dummy heads, different hearing aid positions added (Credit: Florian Denk, Oldenburg) * 03.09.2024: PAN-AR: SRIR dataset for different room and configurations added (Credit: Giorgio Presti and Davide Fantini, Milan) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset for different acoustic room configurations added (Credit: Stephan Werner, Ilmenau) * 05.07.2024: TU Ilmenau: SingleRoomSRIR dataset of a robot's journey through coupled rooms added (Credit: Stephan Werner, Ilmenau) * 27.06.2024: AMU: HRTFs from artificial heads added (Credit: Adrien Vidal, Marseille) * 21.05.2024: BBC Maida Vale Studios: 6 DoF DRIR dataset added (Credit: Jacob Cooper, New York) * 29.08.2023: KAIST-IEM: DRIRs from the KAIST-IEM database added (Credit: Jung-Woo Choi, KAIST, Korea; Franz Zotter, IEM Graz) * 11.07.2023: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.2] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 03.07.2023: AXD: HRTFs from the AXD/SONICOM database added (Credit: Lorenzo Picinali, London) * 02.12.2022: ARI (LAS) database added (Credit: Piotr Majdak & Michael Mihocic, Vienna) * 21.10.2022: [https://www.sofaconventions.org/mediawiki/index.php/Software_and_APIs#SOFA_Toolbox_for_Matlab.2FOctave_.28previously_SOFA_API_Matlab.2FOctave.29 SOFA Toolbox v2.1] was released on [https://sourceforge.net/projects/sofacoustics/ Sourceforge]; the sources are stored at [https://github.com/sofacoustics/sofa github] * 18.07.2022: SCUT: Near-field HRTFs and anthropometric data of listeners * 18.07.2022: CIPIC: Local copy of anthropometric data provided because original site down. * 02.05.2022: CIPIC data fixed * 28.12.2021: Room Transition dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: 6DoF dataset added (Credit: Thomas McKenzie, Aalto) * 28.12.2021: SADIE database added (Credit: Gavin Kearney and Cal Armstrong, York) * 28.12.2021: Listen database added (Credit: Markus Noisternig, Paris) * 28.12.2021: Crossmod database added (Credit: Markus Noisternig, Paris) * 28.12.2021: BiLi database added (Credit: Markus Noisternig, Paris) * 14.12.2021: Application WaveCloud-M removed (broken link, university cannot provide application) * 02.11.2021: sofar, a SOFA API for Python added (Credit: Fabian Brinkmann, Berlin) * 27.10.2021: Application Individualized HRTF Synthesis added to Software and APIs (Credit: Davi Carvalho, Federal University of Santa Maria, Brasil) * 19.10.2021: 3D3A, HRTFs and 3D scans from the Princeton database added (Credit: Edgar Choueiri, USA) * 11.10.2021: Application Webcam Headtracker added to Software and APIs * 02.07.2021: Application Binaural Audio database added to Software and APIs * 28.06.2021: PKU-IOA, High spatial resolution in-the-ear HRTFs added (Credit: Tianshu Qu, China) * 25.06.2021: Several external links updated * 12.02.2021: Test and example files added to files * 02.02.2021: TU Berlin, Directivity HRTFs (sources) added (Credit: David Ackermann, Germany) * 15.01.2021: Aachen, High-resolution HRTFs (human, and KEMAR dummy head) added (Credit: Janina Fels, Aachen) * 27.11.2020: VIKING, Full-sphere HRTFs (.sofa) added (Credit: Simone Spagnol, Denmark) * 04.06.2020: CHEDAR, numerically calculated HRTFs added (Credit: Slim Ghorbal, France) * 07.04.2020: Applications 3D Tune-In Toolkit and Anaglyph added * 31.01.2020: HUTUBS, HRTFs from the HUTUBS database added (Credit: Fabian Brinkmann, Berlin) * 22.01.2020: Widespread (PRTFs and pinna meshes) of 1005 listeners added (Credits: Corentin Guezonoc, CentraleSupélec, Cesson-Sévigné, France) * 15.10.2019: Head-gear HRTFs of a mannequin added (Credits: Christoph Pörschmann, Technische Hochschule Köln, Germany) * 04.07.2019: SOFA for Max: object collection for Max added (Credits: Dale Johnson and Hyunkook Lee, APL, HUD, UK) * 18.06.2019: SOFASonix: Lightweight SOFA API for Python added (Credits: Ioseb Laghidze, Joey Lag, ISVR, Southhampton, UK) * 28.05.2019: pysofaconventions, a SOFA API for Python added (Credits: Andrés Pérez-López, UPF/Eurecat, Spain) * 06.09.2018: pySOFA, a SOFA API for Python added (Credits: Jörg Encke, TUM, Munich) * 05.09.2018: DRIRs from THK added (Credits: Johannes Arend, Tim Lübeck) * 11.06.2018: DirPat (Application) added (Credits: Franz Zotter and the [https://opendata.iem.at/projects/dirpat/ DirPat] team) * 13.11.2017: SBSBRIRs added (Credits: Chris Pike) * 19.07.2017: Aachen HRTF database added (Credits: Janina Fels) * 13.07.2017: WebSofa added to the Software section (Credits: Christian-W. Budde) * 25.05.2017: HRTFs and HpIRs of FABIAN from TU-Berlin added (Credits: Fabian Brinkmann) * 21.11.2016: Near-field HRTFs from the Fachhochschule Köln with 5 different measurement distances * 16.08.2016: Large update of the Oldenburg BRIRs. * 05.03.2015: AES standardization process completed. SOFA 1.0 is now [http://www.aes.org/publications/standards/search.cfm?docID=99 AES69-2015]. * 22.10.2014: Files added: HpIRs from the BT-DEI database provided (Credits: Michele Geronazzo, Italy) * 15.10.2014: Discussion: New datatype "SOS" proposed * 03.10.2014: Files added: Headphone IRs (HpIRs) from the ARI database for over 100 human listeners provided * 11.08.2014: Conventions: SimpleHeadphoneIR 0.1 completed * 23.05.2014: Files added: ARI (ARTIFICIAL), HRTFs of mannequins (dummy heads) measured at ARI using the same setup as for human listeners * 08.04.2014: Files added: ARI B, files with low-frequency content for Hifi listening experience. * 25.03.2014: Files updated: Update to SOFA 0.6 * 20.03.2014: SOFA 0.6 * 21.03.2014: Files added: RIEC Far-field HRTFs from the RIEC database (Credits: Kajni Watanabe, Japan) * 20.03.2014: Conventions: SimpleFreeFieldHRIR 0.4 completed * 27.11.2013: Files added: Near-field HRTFs from SCUT database of the KEMAR (Credits: Bosun Xie, China) * 18.11.2013: Files added: HRTFs of the dummy-head Neumann K100, gapless and high spatial resolution (Credits: Benjamin Bernschütz) * 30.08.2013: SOFA 0.5 * 29.08.2013: Files added: DRIRs from Oldenburg. Recordings in an office under several conditions (Credits: Stephan Ewert) * 29.06.2013: Conventions: GeneralFIR and GeneralTF completed * 21.06.2013: Files added: ARI, LISTEN, CIPIC, MIT KEMAR, TU-Berlin * 20.08.2013: Conventions: SimpleFreeFieldHRIR 0.3 proposed * 17.05.2013: SOFA 0.3 * 17.05.2013: Website released d81d1d3a5f34345b12ef6e86bd17ad283cde24a6 2 575 2628 2025-02-28T17:46:50Z Petibub 4 Creating user page for new user. wikitext text/x-wiki Academy of Medical Engineering and Translational Medicine, Tianjin University, Tianjin,China f27e6254a914c9b25a16317ebb9cd5c0fdb53946 3 576 2629 2025-02-28T17:46:50Z Petibub 4 Welcome! wikitext text/x-wiki '''Welcome to ''Sofaconventions''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Petibub|Petibub]] ([[User talk:Petibub|talk]]) 18:46, 28 February 2025 (CET) bc622ba413b366407b90a19aae228f7d53f271fa